[
https://issues.apache.org/jira/browse/DRILL-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971266#comment-16971266
]
ASF GitHub Bot commented on DRILL-7442:
---------------------------------------
paul-rogers commented on pull request #1897: DRILL-7442: Create multi-batch row
set reader
URL: https://github.com/apache/drill/pull/1897
Adds a ResultSetReader that works across multiple batches
in a result set. Reuses the same row set and readers if
schema is unchanged, creates a new set if the schema changes.
Adds a unit test for the result set reader.
Adds a "rebind" capability to the row set readers to focus
on new buffers under an existing set of vectors. Used when
a new batch arrives, if the schema is unchanged.
Extends row set classses to be aware of the BatchAccessor class
which encapsulates a container and optional selection vector,
and tracks schema changes.
Moves row set tests into the same package as the row sets.
(Row set classes were moved a while back, but the tests were
not moved.)
Renames some BatchAccessor methods.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Create multi-batch row set reader
> ---------------------------------
>
> Key: DRILL-7442
> URL: https://issues.apache.org/jira/browse/DRILL-7442
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Paul Rogers
> Assignee: Paul Rogers
> Priority: Minor
>
> The "row set" work provided a {{RowSetWriter}} and {{RowSetReader}} to write
> to and read from a single batch. The {{ResultSetLoader}} class provided a
> writer that spans multiple batches, handling schema changes across batches
> and so on.
> This ticket introduces a reader equivalent, the {{ResultSetReader}} that
> reads an entire result set of multiple batches, handling schema changes along
> the way.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
