[
https://issues.apache.org/jira/browse/DRILL-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561511#comment-13561511
]
Timothy Chen commented on DRILL-19:
-----------------------------------
I currently ported the Proto transforming into using DescriptorProto, and also
handling Nested schema with Nested types. However, it currently only does Maps
but not lists.
I'm currently not really certain how multi-typed list can be best represented,
as from your (Jacques) previous comment you mentioned about proto definition
into our object graph for free. It only works if we do have a clear schema in
proto def, however currently list's schema can only be encoded into part of the
message since protobuf doesn't support heterogeneous lists.
For lists, the only makes sense DescriptorProto object I can output for now is
just a message that contains bytes:
message List {
required bytes data = 1;
}
Should we try extending protobuf?
> Build a JSON scanner that does schema discovery
> -----------------------------------------------
>
> Key: DRILL-19
> URL: https://issues.apache.org/jira/browse/DRILL-19
> Project: Apache Drill
> Issue Type: New Feature
> Reporter: Jacques Nadeau
> Assignee: Timothy Chen
>
> Build a JSON scanner that reads a file and converts it into two parts: a
> stream of records and a schema which reflects the schema of the records.
--
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
