Uploaded image for project: 'Apache Arrow'
  1. Apache Arrow
  2. ARROW-1047

[Java] Add generalized stream writer and reader interfaces that are decoupled from IO / message framing

    Details

      Description

      cc Julien Le Dem Emilio Lahr-Vivaz Nong Li

      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:

      message ArrowMessagePB {
        required bytes serialized_data;
      }
      

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bryanc Bryan Cutler
                Reporter:
                wesmckinn Wes McKinney
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: