[
https://issues.apache.org/jira/browse/ARROW-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239462#comment-16239462
]
ASF GitHub Bot commented on ARROW-1047:
---------------------------------------
siddharthteotia commented on issue #1259: ARROW-1047: [Java] Add Generic Reader
Interface for Stream Format
URL: https://github.com/apache/arrow/pull/1259#issuecomment-341959674
@BryanCutler, are you suggesting to cherry pick your changes in refactor
branch and revert commit in case things don't look good?
I am not entirely sure what's the best option here but I believe that adding
orthogonal set of changes to java-vector-refactor branch at this point may not
be a good idea. However, I don't want to block other work. So feel free to
proceed based on your best judgement.
Note that there are currently two patches in that branch. While making
changes in Dremio and debugging test failures, I had to go back and make some
changes in vector code (minor only, no redesign). Currently those additional
changes are in Dremio's fork (as I wanted to make quick progress) and I will
put a PR against java-vector-refactor branch for the third patch very soon --
better to do at last when testing with Dremio completes.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> [Java] Add generalized stream writer and reader interfaces that are decoupled
> from IO / message framing
> -------------------------------------------------------------------------------------------------------
>
> Key: ARROW-1047
> URL: https://issues.apache.org/jira/browse/ARROW-1047
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Java - Vectors
> Reporter: Wes McKinney
> Assignee: Bryan Cutler
> Labels: pull-request-available
>
> cc [~julienledem] [~elahrvivaz] [~nongli]
> The ArrowWriter
> https://github.com/apache/arrow/blob/master/java/vector/src/main/java/org/apache/arrow/vector/file/ArrowWriter.java
> accepts a WriteableByteChannel where the stream is written
> It would be useful to be able to support other kinds of message framing and
> transport, like GRPC or HTTP. So rather than writing a complete Arrow stream
> as a single contiguous byte stream, the component messages (schema,
> dictionaries, and record batches) would be framed as separate messages in the
> underlying protocol.
> So if we were using ProtocolBuffers and gRPC as the underlying transport for
> the stream, we could encapsulate components of an Arrow stream in objects
> like:
> {code:language=protobuf}
> message ArrowMessagePB {
> required bytes serialized_data;
> }
> {code}
> If the transport supports zero copy, that is obviously better than
> serializing then parsing a protocol buffer.
> We should do this work in C++ as well to support more flexible stream
> transport.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
