[jira] [Commented] (HIVE-20365) Fix warnings when regenerating thrift code

["Vihang Karajgaonkar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-20365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632606#comment-16632606 ] 

Vihang Karajgaonkar commented on HIVE-20365:
--------------------------------------------

Was out for a while. Picking this up again.. [~asherman] Do you still have concerns? Looks like the API is not yet fully ready and hence it is very unlikely that it is being used in branch-3. Either ways I think we can commit it in 4.0

> Fix warnings when regenerating thrift code
> ------------------------------------------
>
>                 Key: HIVE-20365
>                 URL: https://issues.apache.org/jira/browse/HIVE-20365
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Major
>         Attachments: HIVE-20365.01.patch
>
>
> When you build thrift code you can see thrift warning like below.
> [exec] [WARNING:hive/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift:2167] No field key specified for rqst, resulting protocol may have conflicts or not be backwards compatible!
>  [exec]
>  [exec] [WARNING:hive/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift:2235] No field key specified for o2, resulting protocol may have conflicts or not be backwards compatible!
>  [exec]
>  [exec] [WARNING:hive/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift:2167] No field key specified for rqst, resulting protocol may have conflicts or not be backwards compatible!
>  [exec]
>  [exec] [WARNING:hive/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift:2235] No field key specified for o2, resulting protocol may have conflicts or not be backwards compatible!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)