You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Namit Jain (JIRA)" <ji...@apache.org> on 2009/08/19 02:14:14 UTC
[jira] Created: (HIVE-766) use Thirft for serializing query plan
use Thirft for serializing query plan
-------------------------------------
Key: HIVE-766
URL: https://issues.apache.org/jira/browse/HIVE-766
Project: Hadoop Hive
Issue Type: Improvement
Components: Query Processor
Reporter: Namit Jain
Currently, QueryPlan is serialized using custom code - this has a problem if the thrift interface changes.
Secondly, the deserialization has to be done on the client side - it would be good to use Thrift for serialization/deserialization
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-766) use Thirft for serializing query plan
Posted by "Zheng Shao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745319#action_12745319 ]
Zheng Shao commented on HIVE-766:
---------------------------------
Note that this refers to QueryPlan that contains the counters (see ql/if for details). It does not refer to the plan.xml query plan.
> use Thirft for serializing query plan
> -------------------------------------
>
> Key: HIVE-766
> URL: https://issues.apache.org/jira/browse/HIVE-766
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Namit Jain
>
> Currently, QueryPlan is serialized using custom code - this has a problem if the thrift interface changes.
> Secondly, the deserialization has to be done on the client side - it would be good to use Thrift for serialization/deserialization
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.