[ 
https://issues.apache.org/jira/browse/ARROW-13645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liya Fan updated ARROW-13645:
-----------------------------
    Description: 
As discussed in the ML 
(https://lists.apache.org/thread.html/r19aad8a34f63334d3fcd627106f69be13f689740b83930a4eecc17b3%40%3Cdev.arrow.apache.org%3E),
 the current implementation use hard-coded field names. This may cause some 
problems, for example, when reconstruct a usable schema from a list of 
FieldVectors.

So we resolve this problem by allowing NullVectors to have distinct field 
names. 

This also makes the NullVector with other types of vectors.

  was:
As discussed in the ML 
(https://lists.apache.org/thread.html/r19aad8a34f63334d3fcd627106f69be13f689740b83930a4eecc17b3%40%3Cdev.arrow.apache.org%3E),
 the current implementation use hard-coded field names. This may cause some 
problems, for example, when reconstruct a usable schema from a list of 
FieldVectors.

So we resolve this problem by allowing NullVectors to have distinct field 
names. 


> [Java] Allow NullVectors to have distinct field names
> -----------------------------------------------------
>
>                 Key: ARROW-13645
>                 URL: https://issues.apache.org/jira/browse/ARROW-13645
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Liya Fan
>            Assignee: Liya Fan
>            Priority: Major
>             Fix For: 6.0.0
>
>
> As discussed in the ML 
> (https://lists.apache.org/thread.html/r19aad8a34f63334d3fcd627106f69be13f689740b83930a4eecc17b3%40%3Cdev.arrow.apache.org%3E),
>  the current implementation use hard-coded field names. This may cause some 
> problems, for example, when reconstruct a usable schema from a list of 
> FieldVectors.
> So we resolve this problem by allowing NullVectors to have distinct field 
> names. 
> This also makes the NullVector with other types of vectors.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to