[ https://issues.apache.org/jira/browse/HIVE-20365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632655#comment-16632655 ]
Andrew Sherman commented on HIVE-20365: --------------------------------------- One day we will have to really deal with wire format compatibility. As St Augustine said "Lord, make me pure – but not yet!”. +1 LGTM > 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)