[
https://issues.apache.org/jira/browse/HIVE-25490?focusedWorklogId=663750&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-663750
]
ASF GitHub Bot logged work on HIVE-25490:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Oct/21 20:11
Start Date: 11/Oct/21 20:11
Worklog Time Spent: 10m
Work Description: saihemanth-cloudera closed pull request #2622:
URL: https://github.com/apache/hive/pull/2622
--
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 663750)
Time Spent: 20m (was: 10m)
> Table object should be authorized with owner info in the get_partitions() api
> in HMS
> ------------------------------------------------------------------------------------
>
> Key: HIVE-25490
> URL: https://issues.apache.org/jira/browse/HIVE-25490
> Project: Hive
> Issue Type: Bug
> Components: Hive, Standalone Metastore
> Reporter: Sai Hemanth Gantasala
> Assignee: Sai Hemanth Gantasala
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> HiveMetaStore#get_partitions() api is currently authorizing against table
> name. Instead, the table object should be authorized so that it also has
> table_owner information in the table object.
> Currently, a user from spark-shell running these commands (in a rangerized
> environment):
> > spark.sql( " create database 791237_db1 " ).show(false)
> > spark.sql( " CREATE EXTERNAL TABLE IF NOT EXISTS 791237_db1.t1(cal_dt
> >timestamp) PARTITIONED BY (year string) stored as parquet location
> >'/791237/791237_db1' " ).show(false)
> > spark.sql( " select * from 791237_db1.t1 " ).show(false)
> ERROR metadata.Hive: NoSuchObjectException(message:Table t1 does not exist)
> Even though the user is the owner of the table, but the same user cannot
> query the table. This should be addressed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
