[jira] [Updated] (ARROW-326) [Java] ComplexWriter should initialize nested writers when container vector is already populated

["Wes McKinney (JIRA)" <ji...@apache.org>]

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

Wes McKinney updated ARROW-326:
-------------------------------
    Summary: [Java] ComplexWriter should initialize nested writers when container vector is already populated  (was: ComplexWriter should initialize nested writers when container vector is already populated)

> [Java] ComplexWriter should initialize nested writers when container vector is already populated
> ------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-326
>                 URL: https://issues.apache.org/jira/browse/ARROW-326
>             Project: Apache Arrow
>          Issue Type: Bug
>            Reporter: Steven Phillips
>            Assignee: Steven Phillips
>            Priority: Major
>
> It's possible and sometimes useful to use reuse a nested vector that was populated in a previous ComplexWriter. The new ComplexWriter should be aware of the fields that are present in the vector.
> As it is right now, if a particular column were determined to be a specific type (or a union type), but the new writer finds a new type, the original type may be thrown out. What should happen is that the type should be promoted to union (or have a new subtype added to the union field).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)