Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@arrow.apache.org
Date: Fri, 7 Oct 2016 20:13:20 +0000 (UTC)
From: "Steven Phillips (JIRA)" <jira@apache.org>
To: dev@arrow.apache.org
Message-ID: <JIRA.13010587.1475871140000.767333.1475871200426@Atlassian.JIRA>
In-Reply-To: <JIRA.13010587.1475871140000@Atlassian.JIRA>
References: <JIRA.13010587.1475871140000@Atlassian.JIRA> <JIRA.13010587.1475871140554@arcas>
Subject: [jira] [Created] (ARROW-326) ComplexWriter should initialize nested
 writers when container vector is already populated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 07 Oct 2016 20:13:22 -0000

Steven Phillips created ARROW-326:
-------------------------------------

             Summary: 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


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
(v6.3.4#6332)