[
https://issues.apache.org/jira/browse/ARROW-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17657360#comment-17657360
]
Rok Mihevc commented on ARROW-326:
----------------------------------
This issue has been migrated to [issue
#15788|https://github.com/apache/arrow/issues/15788] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [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
> Components: Java
> Reporter: 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
(v8.20.10#820010)
