tMilvusOutput

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Click Sync columns to retrieve the schema from the previous component connected in the Job.

Enter the name, in double quotation marks, of the partition column of the Milvus table you want to perform the operation on, or click the [...] button next to the corresponding field to select the desired one.

You can only define one value.

NB_LINE: the number of rows read by an input component or transferred to an output component. This is an After variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

• tMilvusOutput executes the action defined on the collection in the Milvus database based on the flow incoming from the preceding component in the Job.
• tMilvusOutput supports query vector capabilities, you can use it to perform actions on vector embeddings. For more information on vector embeddings, see the corresponding Milvus documentation.