[
https://issues.apache.org/jira/browse/HIVE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghotham Murthy updated HIVE-73:
---------------------------------
Attachment: hive-73.3.txt
Attaching a smaller diff file without any of the generated code or include
files. This should be useful to actually review the code. Note that this file
is not the complete patch. I'll upload another file with the full diff after
review comments.
In this patch, the schema of the result is now available at the server. It
required some hacking of the hive/ql code since there is currently no way to
access the schema of the result of a query.
The plan is for the JDBC or other clients to instantiate a DynamicSerDe with
the schema string that is returned by the server. The row returned by the
server is actually serialized using the MetadataTypedColumnSetSerDe. Pete
mentioned that DynamicSerDe can deserialize this row if it is initialized with
the right schema and protocol. I'll add that next.
> Thrift Server and Client for Hive
> ---------------------------------
>
> Key: HIVE-73
> URL: https://issues.apache.org/jira/browse/HIVE-73
> Project: Hadoop Hive
> Issue Type: New Feature
> Affects Versions: 0.20.0
> Reporter: Raghotham Murthy
> Assignee: Raghotham Murthy
> Fix For: 0.20.0
>
> Attachments: hive-73.1.patch, hive-73.2.patch, hive-73.3.txt
>
>
> Currently the hive cli directly calls the driver code. We need to be able to
> run a stand alone hive server that multiple clients can connect to. The hive
> server will allow clients to run queries as well as make meta data calls (by
> inheriting from the thrift metastore server)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
