[ 
https://issues.apache.org/jira/browse/ARROW-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259607#comment-16259607
 ] 

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-345785258
 
 
   @BryanCutler , I would like to test this with Dremio but I am not sure how 
quickly I will be able to do that and revert back after making necessary 
changes in Dremio and doing proper testing. 
   
   Part of me says you should go ahead and merge this since you were already 
waiting for the refactor work to get done before this. 
   
   Since we will anyway have to rebase on Arrow master after the ongoing 
timestamp vector related changes in https://github.com/apache/arrow/pull/1330, 
we can take care of testing this out with Dremio at that time unless @jacques-n 
thinks otherwise?
   

----------------------------------------------------------------
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)

Reply via email to