You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/12 14:05:02 UTC

[jira] [Assigned] (ARROW-9614) [Java] JDBC to Arrow converter iterator should reuse the same VectorSchemaRoot

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

Todd Farmer reassigned ARROW-9614:
----------------------------------

    Assignee:     (was: Ji Liu)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [Java] JDBC to Arrow converter iterator should reuse the same VectorSchemaRoot
> ------------------------------------------------------------------------------
>
>                 Key: ARROW-9614
>                 URL: https://issues.apache.org/jira/browse/ARROW-9614
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Micah Kornfield
>            Priority: Major
>
> When originally reviewing the code I suggested a new VectorSchemaRoot on each call to the iterator.  After further discussions on the mailing list, it seems that this is an anit-pattern for working with VectorSchemaRoot, we should update the code to update a single VectorSchemaRoot.
>  
> After this change it should be easier to use JDBC converter with other components of the library (i.e. filewriter) which also make use of a single VectorSchemaRoot.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)