[
https://issues.apache.org/jira/browse/DRILL-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601367#comment-13601367
]
Jacques Nadeau commented on DRILL-48:
-------------------------------------
The current experimentation I've been doing with execution wire-level and
memory formats have been utilizing protobuf. Part of this has to do with the
previous adoption of protobuf as the wire format within hadoop and hbase. Part
of it has to do with the strong documentation, my previous positive experiences
and the CodedInputStream and CodedOutputStream interfaces. At some level, if
we define a strong IDL, they are all kind of the same. The biggest challenge I
had with Avro historically was the lack of the clear IDL and quality of the
bindings for other languages (although I think those things have been mitigated
more recently). It sounds like David is signing up to do some of these things
so maybe he and I can work on some designs about getting distributed execution
working and solve it in-mode.
Random observation/aside on the Avro and Trevni thing. With the rise of
Parquet and ORC, it seems more and more like Trevni is being passed over.
> RPC interface for query submission and physical plan execution
> --------------------------------------------------------------
>
> Key: DRILL-48
> URL: https://issues.apache.org/jira/browse/DRILL-48
> Project: Apache Drill
> Issue Type: Task
> Reporter: David Alves
>
> Now that drill has a minimal set of functions that allow to actually execute
> something we should come up with the RPC interface that will sit in front of
> the daemons and to which queries in various formats wil be submitted.
> It would need to allow for the following:
> - submit queries
> - submit logical plans
> - submit physical plans for execution
> - query underlying storage engines for metadata and statistics
> - possibly serve as a frontend to a metadata store
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
