[ 
https://issues.apache.org/jira/browse/HIVE-24608?focusedWorklogId=596782&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-596782
 ]

ASF GitHub Bot logged work on HIVE-24608:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/May/21 17:16
            Start Date: 14/May/21 17:16
    Worklog Time Spent: 10m 
      Work Description: szehon-ho commented on pull request #2080:
URL: https://github.com/apache/hive/pull/2080#issuecomment-841386933


   Sounds good, and I got the write access :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 596782)
    Time Spent: 1h  (was: 50m)

> Switch back to get_table in HMS client for Hive 2.3.x
> -----------------------------------------------------
>
>                 Key: HIVE-24608
>                 URL: https://issues.apache.org/jira/browse/HIVE-24608
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 2.3.7
>            Reporter: Chao Sun
>            Assignee: Chao Sun
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.3.9
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> HIVE-15062 introduced a backward-incompatible change by replacing 
> {{get_table}} with {{get_table_req}}. As consequence, when HMS client w/ 
> version > 2.3 talks to a HMS w/ version < 2.3, it will get error similar to 
> the following:
> {code}
> AnalysisException: org.apache.hadoop.hive.ql.metadata.HiveException: Unable 
> to fetch table testpartitiondata. Invalid method name: 'get_table_req';
> {code}
> Looking at HIVE-15062, the {{get_table_req}} is to introduce client-side 
> check for capabilities. However in branch-2.3 the check is a no-op since 
> there is no capability yet (it is assigned to null). Therefore, this JIRA 
> proposes to switch back to {{get_table}} in branch-2.3 to fix the 
> compatibility issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to