You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, milvus has added support for the special data type of null, so it is necessary to support the parsing of null values in csv format in the bulkinsert function.
csv is a text data format, and there is no specific data type corresponding to null, so the implementation idea is to use a configurable special string to represent the null value. If this special string is matched, then this field will be parsed as null.
In addition, the array type supports null, but the elements in the array do not support null, as shown in the following example
// support
arr := NULL
// not support
arr := [1, 2, NULL, 4]
nullkey configuartion
In csv format, parsing of null identifiers can be configured. The field name is nullkey, which currently supports any string. If not configured, the default is nullkey = "" .
Is there an existing issue for this?
What would you like to be added?
Recently, milvus has added support for the special data type of null, so it is necessary to support the parsing of null values in csv format in the bulkinsert function.
csv is a text data format, and there is no specific data type corresponding to null, so the implementation idea is to use a configurable special string to represent the null value. If this special string is matched, then this field will be parsed as null.
Data types that support null values
Currently the data types that support null are
The data types that do not support null are
In addition, the
array
type supports null, but the elements in the array do not support null, as shown in the following examplenullkey configuartion
In csv format, parsing of null identifiers can be configured. The field name is
nullkey
, which currently supports any string. If not configured, the default isnullkey = ""
.Why is this needed?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: