Neer393 opened a new pull request, #6314:
URL: https://github.com/apache/hive/pull/6314

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
     2. Ensure that you have created an issue on the Hive project JIRA: 
https://issues.apache.org/jira/projects/HIVE/summary
     3. Ensure you have added or run the appropriate tests for your PR: 
     4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP]HIVE-XXXXX:  Your PR title ...'.
     5. Be sure to keep the PR description updated to reflect all changes.
     6. Please write your PR title to summarize what this PR proposes.
     7. If possible, provide a concise example to reproduce the issue for a 
faster review.
   
   -->
   
   ### What changes were proposed in this pull request?
   Modified SHowLocksRequest and ShowLocksResponse to include the catalog name 
and modified the grammar to accept catalog name for getting locks. Added a 
catalog field to the HMS HIVE_LOCKS table for 4.3.0 and added an alter 
statement for upgrading from 4.2.0 to 4.3.0
   
   
   ### Why are the changes needed?
   The changes are needed so that now user can view locks on tables and 
databases across catalogs.
   
   
   ### Does this PR introduce _any_ user-facing change?
   No user facing change
   
   ### How was this patch tested?
   Checked the HIVE_LOCKS table and it had the Catalog column and also tried 
`SHOW LOCKS DATABASE dbname;` which displayed the catalog column as well. Also 
tried out `SHOW LOCKS DATABASE catname.dbname;`
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to