[jira] [Updated] (HIVE-11175) create function using jar does not work with sql std authorization
[
https://issues.apache.org/jira/browse/HIVE-11175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olaf Flebbe updated HIVE-11175:
---
Status: Open (was: Patch Available)
> create function using jar does not work with sql std authorization
> --
>
> Key: HIVE-11175
> URL: https://issues.apache.org/jira/browse/HIVE-11175
> Project: Hive
> Issue Type: Bug
> Components: Authorization
>Affects Versions: 1.2.0
>Reporter: Olaf Flebbe
>Assignee: Olaf Flebbe
>Priority: Major
> Attachments: HIVE-11175.1.patch
>
>
> {code:sql}create function xxx as 'xxx' using jar 'file://foo.jar' {code}
> gives error code for need of accessing a local foo.jar resource with ADMIN
> privileges. Same for HDFS (DFS_URI) .
> problem is that the semantic analysis enforces the ADMIN privilege for write
> but the jar is clearly input not output.
> Patch und Testcase appendend.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HIVE-11175) create function using jar does not work with sql std authorization
[
https://issues.apache.org/jira/browse/HIVE-11175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olaf Flebbe resolved HIVE-11175.
Resolution: Won't Fix
> create function using jar does not work with sql std authorization
> --
>
> Key: HIVE-11175
> URL: https://issues.apache.org/jira/browse/HIVE-11175
> Project: Hive
> Issue Type: Bug
> Components: Authorization
>Affects Versions: 1.2.0
>Reporter: Olaf Flebbe
>Assignee: Olaf Flebbe
>Priority: Major
> Attachments: HIVE-11175.1.patch
>
>
> {code:sql}create function xxx as 'xxx' using jar 'file://foo.jar' {code}
> gives error code for need of accessing a local foo.jar resource with ADMIN
> privileges. Same for HDFS (DFS_URI) .
> problem is that the semantic analysis enforces the ADMIN privilege for write
> but the jar is clearly input not output.
> Patch und Testcase appendend.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HIVE-20543) Support replication of Materialized views
[ https://issues.apache.org/jira/browse/HIVE-20543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan reassigned HIVE-20543: --- Assignee: Aasha Medhi (was: Sankar Hariappan) > Support replication of Materialized views > - > > Key: HIVE-20543 > URL: https://issues.apache.org/jira/browse/HIVE-20543 > Project: Hive > Issue Type: Sub-task > Components: Materialized views, repl >Affects Versions: 4.0.0, 3.2.0 >Reporter: Sankar Hariappan >Assignee: Aasha Medhi >Priority: Major > Labels: DR, Replication > > Currently materialized views are replicated but doesn't work if the DB is > renamed after load. Also, it doesn't replicate ALTER MATERIALIZED VIEW > [db_name.]materialized_view_name REBUILD; command so that MV remains stale > and not in sync with source. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-21530) Replicate Streaming ingestion with transactions batch size greater than 1.
[ https://issues.apache.org/jira/browse/HIVE-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan reassigned HIVE-21530: --- Assignee: Pravin Sinha (was: Sankar Hariappan) > Replicate Streaming ingestion with transactions batch size greater than 1. > -- > > Key: HIVE-21530 > URL: https://issues.apache.org/jira/browse/HIVE-21530 > Project: Hive > Issue Type: Bug > Components: repl, Transactions >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Pravin Sinha >Priority: Major > Labels: DR, Replication > Attachments: Hive ACID Replication_ Streaming Ingest Tables.pdf > > > implement replication of hive streaming ingest of tables as per [^Hive ACID > Replication_ Streaming Ingest Tables.pdf] . > changes to txn_commit to include information about transaction batch. > changes to copy task to only copy if there is a difference in file size or > checksum, seems specific to transaction batch shouldnt be used for normal > transactions. > copy the correct sequence of files w.r.t data file + side file. > remove side files ( which looks like are suffixed as _flush in file names) > when the batch is committed. > how do we determine the idempotent nature of the events here, update the > corresponding table + partition and not copy new version of the file. > validate if partial copied data files are handled on the target warehouse > given correct side file. can we leave the side file file forever, in case > during transaction batch copy after certain transactions are copied over then > primary warehouse fails. we wont be able to remove _flush file, on failover > do we have to handle this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-16218) Replicate views with proper query string when perform REPL LOAD on a renamed database.
[ https://issues.apache.org/jira/browse/HIVE-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan reassigned HIVE-16218: --- Assignee: Aasha Medhi (was: Sankar Hariappan) > Replicate views with proper query string when perform REPL LOAD on a renamed > database. > -- > > Key: HIVE-16218 > URL: https://issues.apache.org/jira/browse/HIVE-16218 > Project: Hive > Issue Type: Sub-task > Components: repl >Reporter: Sankar Hariappan >Assignee: Aasha Medhi >Priority: Minor > > If REPL LOAD is applied on a renamed database, then need to update the alias > query string (part of view original and expanded text in Table object) to > point to destination database name else the view will still run the query on > source database. > While creating the CreateViewDesc part of ImportDesc instantiation should > take care of this. > This ticket is a follow up of parent JIRA HIVE-15556. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-21893) Handle concurrent write + drop when ACID tables are getting bootstrapped.
[ https://issues.apache.org/jira/browse/HIVE-21893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan reassigned HIVE-21893: --- Assignee: Aasha Medhi (was: Sankar Hariappan) > Handle concurrent write + drop when ACID tables are getting bootstrapped. > - > > Key: HIVE-21893 > URL: https://issues.apache.org/jira/browse/HIVE-21893 > Project: Hive > Issue Type: Bug > Components: repl >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Aasha Medhi >Priority: Major > Labels: DR, Replication > > ACID tables will be bootstrapped during incremental phase in couple of cases. > 1. hive.repl.bootstrap.acid.tables is set to true in WITH clause of REPL DUMP. > 2. If replication policy is changed using REPLACE clause in REPL DUMP where > the ACID table is matching new policy but not old policy. > REPL DUMP performed below sequence of operations. Let's say Thread (T1) > 1. Get Last Repl ID (lastId) > 2. Open Transaction (Tx1) > 3. Dump events until lastId. > 4. Get the list of tables in the given DB. > 5. If table matches current policy, then bootstrap dump it. > Let's say, concurrently another thread (let's say T2) is running as follows. > 11. Open Transaction (Tx2). > 12. Insert into ACID table Tbl1. > 13. Commit Transaction (Tx2) > 14. Drop table (Tbl1) --> Not necessarily same thread, may be from different > thread as well. > *Problematic Use-cases:* > 1. If Step-11 happens between Step-1 and Step-2. Also, Step-13 completes > before we forcefully abort Tx2 from REPL DUMP thread T1. Also, assume Step-14 > is done after bootstrap is completed. In this case, bootstrap would replicate > the data/writeId written by Tx2. But, the next incremental cycle would also > replicate the open_txn, allocate_writeid and commit_txn events which would > duplicate the data. > 2. If Step-11 to Step-14 in Thread T2 happens after Step-1 in REPL DUMP > thread T1. In this case, table is not bootstrapped but the corresponding > open_txn, allocate_writeid, commit_txn and drop events would be replicated in > next cycle. During next cycle, REPL LOAD would fail on commmitTxn event as > table is dropped or event is missing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HIVE-23887) Reset table level basic/column stats during import.
[ https://issues.apache.org/jira/browse/HIVE-23887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-23887. - Fix Version/s: 4.0.0 Target Version/s: 4.0.0 Resolution: Fixed > Reset table level basic/column stats during import. > --- > > Key: HIVE-23887 > URL: https://issues.apache.org/jira/browse/HIVE-23887 > Project: Hive > Issue Type: Bug > Components: Import/Export, Statistics >Reporter: Ashish Sharma >Assignee: Ashish Sharma >Priority: Minor > Labels: pull-request-available > Fix For: 4.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > While doing "export table db.table to '/import/table' " column stats are not > dumped but import doesn't reset the flag which leads to incorrect stats. > Reset columns stats while import to force Imported to recalculate the Columns > stats -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-23887) Reset table level basic/column stats during import.
[ https://issues.apache.org/jira/browse/HIVE-23887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-23887: Affects Version/s: 4.0.0 > Reset table level basic/column stats during import. > --- > > Key: HIVE-23887 > URL: https://issues.apache.org/jira/browse/HIVE-23887 > Project: Hive > Issue Type: Bug > Components: Import/Export, Statistics >Affects Versions: 4.0.0 >Reporter: Ashish Sharma >Assignee: Ashish Sharma >Priority: Minor > Labels: pull-request-available > Fix For: 4.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > While doing "export table db.table to '/import/table' " column stats are not > dumped but import doesn't reset the flag which leads to incorrect stats. > Reset columns stats while import to force Imported to recalculate the Columns > stats -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-23887) Reset table level basic/column stats during import.
[ https://issues.apache.org/jira/browse/HIVE-23887?focusedWorklogId=473345=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-473345 ] ASF GitHub Bot logged work on HIVE-23887: - Author: ASF GitHub Bot Created on: 21/Aug/20 16:53 Start Date: 21/Aug/20 16:53 Worklog Time Spent: 10m Work Description: sankarh merged pull request #1370: URL: https://github.com/apache/hive/pull/1370 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: 473345) Time Spent: 1.5h (was: 1h 20m) > Reset table level basic/column stats during import. > --- > > Key: HIVE-23887 > URL: https://issues.apache.org/jira/browse/HIVE-23887 > Project: Hive > Issue Type: Bug > Components: Import/Export, Statistics >Reporter: Ashish Sharma >Assignee: Ashish Sharma >Priority: Minor > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > While doing "export table db.table to '/import/table' " column stats are not > dumped but import doesn't reset the flag which leads to incorrect stats. > Reset columns stats while import to force Imported to recalculate the Columns > stats -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
[ https://issues.apache.org/jira/browse/HIVE-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan reassigned HIVE-12679: --- Assignee: Noritaka Sekiyama (was: Sankar Hariappan) > Allow users to be able to specify an implementation of IMetaStoreClient via > HiveConf > > > Key: HIVE-12679 > URL: https://issues.apache.org/jira/browse/HIVE-12679 > Project: Hive > Issue Type: Improvement > Components: Configuration, Metastore, Query Planning >Reporter: Austin Lee >Assignee: Noritaka Sekiyama >Priority: Minor > Labels: metastore, pull-request-available > Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch, > HIVE-12679.branch-1.2.patch, HIVE-12679.branch-2.3.patch, HIVE-12679.patch > > Time Spent: 50m > Remaining Estimate: 0h > > Hi, > I would like to propose a change that would make it possible for users to > choose an implementation of IMetaStoreClient via HiveConf, i.e. > hive-site.xml. Currently, in Hive the choice is hard coded to be > SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There > is no other direct reference to SessionHiveMetaStoreClient other than the > hard coded class name in Hive.java and the QL component operates only on the > IMetaStoreClient interface so the change would be minimal and it would be > quite similar to how an implementation of RawStore is specified and loaded in > hive-metastore. One use case this change would serve would be one where a > user wishes to use an implementation of this interface without the dependency > on the Thrift server. > > Thank you, > Austin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
[ https://issues.apache.org/jira/browse/HIVE-12679?focusedWorklogId=473339=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-473339 ] ASF GitHub Bot logged work on HIVE-12679: - Author: ASF GitHub Bot Created on: 21/Aug/20 16:41 Start Date: 21/Aug/20 16:41 Worklog Time Spent: 10m Work Description: sankarh removed a comment on pull request #1402: URL: https://github.com/apache/hive/pull/1402#issuecomment-678378941 Patch LGTM Thanks @moomindani! 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: 473339) Time Spent: 50m (was: 40m) > Allow users to be able to specify an implementation of IMetaStoreClient via > HiveConf > > > Key: HIVE-12679 > URL: https://issues.apache.org/jira/browse/HIVE-12679 > Project: Hive > Issue Type: Improvement > Components: Configuration, Metastore, Query Planning >Reporter: Austin Lee >Priority: Minor > Labels: metastore, pull-request-available > Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch, > HIVE-12679.branch-1.2.patch, HIVE-12679.branch-2.3.patch, HIVE-12679.patch > > Time Spent: 50m > Remaining Estimate: 0h > > Hi, > I would like to propose a change that would make it possible for users to > choose an implementation of IMetaStoreClient via HiveConf, i.e. > hive-site.xml. Currently, in Hive the choice is hard coded to be > SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There > is no other direct reference to SessionHiveMetaStoreClient other than the > hard coded class name in Hive.java and the QL component operates only on the > IMetaStoreClient interface so the change would be minimal and it would be > quite similar to how an implementation of RawStore is specified and loaded in > hive-metastore. One use case this change would serve would be one where a > user wishes to use an implementation of this interface without the dependency > on the Thrift server. > > Thank you, > Austin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
[ https://issues.apache.org/jira/browse/HIVE-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan reassigned HIVE-12679: --- Assignee: Sankar Hariappan > Allow users to be able to specify an implementation of IMetaStoreClient via > HiveConf > > > Key: HIVE-12679 > URL: https://issues.apache.org/jira/browse/HIVE-12679 > Project: Hive > Issue Type: Improvement > Components: Configuration, Metastore, Query Planning >Reporter: Austin Lee >Assignee: Sankar Hariappan >Priority: Minor > Labels: metastore, pull-request-available > Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch, > HIVE-12679.branch-1.2.patch, HIVE-12679.branch-2.3.patch, HIVE-12679.patch > > Time Spent: 50m > Remaining Estimate: 0h > > Hi, > I would like to propose a change that would make it possible for users to > choose an implementation of IMetaStoreClient via HiveConf, i.e. > hive-site.xml. Currently, in Hive the choice is hard coded to be > SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There > is no other direct reference to SessionHiveMetaStoreClient other than the > hard coded class name in Hive.java and the QL component operates only on the > IMetaStoreClient interface so the change would be minimal and it would be > quite similar to how an implementation of RawStore is specified and loaded in > hive-metastore. One use case this change would serve would be one where a > user wishes to use an implementation of this interface without the dependency > on the Thrift server. > > Thank you, > Austin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
[ https://issues.apache.org/jira/browse/HIVE-12679?focusedWorklogId=473338=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-473338 ] ASF GitHub Bot logged work on HIVE-12679: - Author: ASF GitHub Bot Created on: 21/Aug/20 16:36 Start Date: 21/Aug/20 16:36 Worklog Time Spent: 10m Work Description: sankarh commented on pull request #1402: URL: https://github.com/apache/hive/pull/1402#issuecomment-678382353 I would like to bring up the comment from @thejasmn which sounds valid to me. "Note that SessionHiveMetaStoreClient implements logic for temp tables, as they have a lifetime of a session. I am wondering if this config should determine which IMetaStoreClient impl is used by SessionHiveMetaStoreClient, instead of replacing SessionHiveMetaStoreClient itself. Some changes to SessionHiveMetaStoreClient would be needed as well for that approach, for it to accept configured IMetaStoreClient." Would you pls address this comment? 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: 473338) Time Spent: 40m (was: 0.5h) > Allow users to be able to specify an implementation of IMetaStoreClient via > HiveConf > > > Key: HIVE-12679 > URL: https://issues.apache.org/jira/browse/HIVE-12679 > Project: Hive > Issue Type: Improvement > Components: Configuration, Metastore, Query Planning >Reporter: Austin Lee >Priority: Minor > Labels: metastore, pull-request-available > Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch, > HIVE-12679.branch-1.2.patch, HIVE-12679.branch-2.3.patch, HIVE-12679.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Hi, > I would like to propose a change that would make it possible for users to > choose an implementation of IMetaStoreClient via HiveConf, i.e. > hive-site.xml. Currently, in Hive the choice is hard coded to be > SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There > is no other direct reference to SessionHiveMetaStoreClient other than the > hard coded class name in Hive.java and the QL component operates only on the > IMetaStoreClient interface so the change would be minimal and it would be > quite similar to how an implementation of RawStore is specified and loaded in > hive-metastore. One use case this change would serve would be one where a > user wishes to use an implementation of this interface without the dependency > on the Thrift server. > > Thank you, > Austin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
[ https://issues.apache.org/jira/browse/HIVE-12679?focusedWorklogId=473335=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-473335 ] ASF GitHub Bot logged work on HIVE-12679: - Author: ASF GitHub Bot Created on: 21/Aug/20 16:35 Start Date: 21/Aug/20 16:35 Worklog Time Spent: 10m Work Description: sankarh edited a comment on pull request #1402: URL: https://github.com/apache/hive/pull/1402#issuecomment-678378941 Patch LGTM Thanks @moomindani! 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: 473335) Time Spent: 0.5h (was: 20m) > Allow users to be able to specify an implementation of IMetaStoreClient via > HiveConf > > > Key: HIVE-12679 > URL: https://issues.apache.org/jira/browse/HIVE-12679 > Project: Hive > Issue Type: Improvement > Components: Configuration, Metastore, Query Planning >Reporter: Austin Lee >Priority: Minor > Labels: metastore, pull-request-available > Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch, > HIVE-12679.branch-1.2.patch, HIVE-12679.branch-2.3.patch, HIVE-12679.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Hi, > I would like to propose a change that would make it possible for users to > choose an implementation of IMetaStoreClient via HiveConf, i.e. > hive-site.xml. Currently, in Hive the choice is hard coded to be > SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There > is no other direct reference to SessionHiveMetaStoreClient other than the > hard coded class name in Hive.java and the QL component operates only on the > IMetaStoreClient interface so the change would be minimal and it would be > quite similar to how an implementation of RawStore is specified and loaded in > hive-metastore. One use case this change would serve would be one where a > user wishes to use an implementation of this interface without the dependency > on the Thrift server. > > Thank you, > Austin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
[ https://issues.apache.org/jira/browse/HIVE-12679?focusedWorklogId=473332=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-473332 ] ASF GitHub Bot logged work on HIVE-12679: - Author: ASF GitHub Bot Created on: 21/Aug/20 16:28 Start Date: 21/Aug/20 16:28 Worklog Time Spent: 10m Work Description: sankarh commented on pull request #1402: URL: https://github.com/apache/hive/pull/1402#issuecomment-678378941 +1 Patch LGTM Thanks @moomindani! 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: 473332) Time Spent: 20m (was: 10m) > Allow users to be able to specify an implementation of IMetaStoreClient via > HiveConf > > > Key: HIVE-12679 > URL: https://issues.apache.org/jira/browse/HIVE-12679 > Project: Hive > Issue Type: Improvement > Components: Configuration, Metastore, Query Planning >Reporter: Austin Lee >Priority: Minor > Labels: metastore, pull-request-available > Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch, > HIVE-12679.branch-1.2.patch, HIVE-12679.branch-2.3.patch, HIVE-12679.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Hi, > I would like to propose a change that would make it possible for users to > choose an implementation of IMetaStoreClient via HiveConf, i.e. > hive-site.xml. Currently, in Hive the choice is hard coded to be > SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There > is no other direct reference to SessionHiveMetaStoreClient other than the > hard coded class name in Hive.java and the QL component operates only on the > IMetaStoreClient interface so the change would be minimal and it would be > quite similar to how an implementation of RawStore is specified and loaded in > hive-metastore. One use case this change would serve would be one where a > user wishes to use an implementation of this interface without the dependency > on the Thrift server. > > Thank you, > Austin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HIVE-24056) Column stats gather stage as part of import table command plan generation
[ https://issues.apache.org/jira/browse/HIVE-24056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-24056 started by Ashish Sharma. > Column stats gather stage as part of import table command plan generation > -- > > Key: HIVE-24056 > URL: https://issues.apache.org/jira/browse/HIVE-24056 > Project: Hive > Issue Type: Improvement > Components: Import/Export, Statistics >Reporter: Ashish Sharma >Assignee: Ashish Sharma >Priority: Major > > Description - > As of today in import table command does't have column stats gather phase as > a part of execution plan. As a result of which no matter what > hive.stats.autogather set to true or false. columns stats are reset while > importing the table/partitions for all types of tables. > DOD > Adding column stats gather stage to import plan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-24056) Column stats gather stage as part of import table command plan generation
[ https://issues.apache.org/jira/browse/HIVE-24056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Sharma reassigned HIVE-24056: > Column stats gather stage as part of import table command plan generation > -- > > Key: HIVE-24056 > URL: https://issues.apache.org/jira/browse/HIVE-24056 > Project: Hive > Issue Type: Improvement > Components: Import/Export, Statistics >Reporter: Ashish Sharma >Assignee: Ashish Sharma >Priority: Major > > Description - > As of today in import table command does't have column stats gather phase as > a part of execution plan. As a result of which no matter what > hive.stats.autogather set to true or false. columns stats are reset while > importing the table/partitions for all types of tables. > DOD > Adding column stats gather stage to import plan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-24055) Admin role do not have admin privilege when using hive client
[ https://issues.apache.org/jira/browse/HIVE-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongyixuan updated HIVE-24055: -- Attachment: image-2020-08-21-18-53-26-910.png > Admin role do not have admin privilege when using hive client > - > > Key: HIVE-24055 > URL: https://issues.apache.org/jira/browse/HIVE-24055 > Project: Hive > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: hive 2.3.2 > centos 7 >Reporter: gongyixuan >Priority: Critical > Attachments: image-2020-08-21-18-53-26-910.png > > > When judge a user is a admin role or not ，the currentRoles not initialized > correctly. > User zdp is admin role , but not be included in currentRoles，making > isUserAdmin() return false. > !image-2020-08-21-18-43-00-677.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-24055) Admin role do not have admin privilege when using hive client
[ https://issues.apache.org/jira/browse/HIVE-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongyixuan updated HIVE-24055: -- Description: When judge a user is a admin role or not ，the currentRoles not initialized correctly. User zdp is admin role , but not be included in currentRoles，making isUserAdmin() return false. !image-2020-08-21-18-53-26-910.png! was: When judge a user is a admin role or not ，the currentRoles not initialized correctly. User zdp is admin role , but not be included in currentRoles，making isUserAdmin() return false. !image-2020-08-21-18-43-00-677.png! > Admin role do not have admin privilege when using hive client > - > > Key: HIVE-24055 > URL: https://issues.apache.org/jira/browse/HIVE-24055 > Project: Hive > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: hive 2.3.2 > centos 7 >Reporter: gongyixuan >Priority: Critical > Attachments: image-2020-08-21-18-53-26-910.png > > > When judge a user is a admin role or not ，the currentRoles not initialized > correctly. > User zdp is admin role , but not be included in currentRoles，making > isUserAdmin() return false. > !image-2020-08-21-18-53-26-910.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-24055) Admin role do not have admin privilege when using hive client
[ https://issues.apache.org/jira/browse/HIVE-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongyixuan updated HIVE-24055: -- Attachment: (was: image-2020-08-21-18-43-00-677.png) > Admin role do not have admin privilege when using hive client > - > > Key: HIVE-24055 > URL: https://issues.apache.org/jira/browse/HIVE-24055 > Project: Hive > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: hive 2.3.2 > centos 7 >Reporter: gongyixuan >Priority: Critical > Attachments: image-2020-08-21-18-53-26-910.png > > > When judge a user is a admin role or not ，the currentRoles not initialized > correctly. > User zdp is admin role , but not be included in currentRoles，making > isUserAdmin() return false. > !image-2020-08-21-18-53-26-910.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-24055) Admin role do not have admin privilege when using hive client
[ https://issues.apache.org/jira/browse/HIVE-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongyixuan updated HIVE-24055: -- Attachment: (was: image-2020-08-21-18-53-22-094.png) > Admin role do not have admin privilege when using hive client > - > > Key: HIVE-24055 > URL: https://issues.apache.org/jira/browse/HIVE-24055 > Project: Hive > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: hive 2.3.2 > centos 7 >Reporter: gongyixuan >Priority: Critical > Attachments: image-2020-08-21-18-53-26-910.png > > > When judge a user is a admin role or not ，the currentRoles not initialized > correctly. > User zdp is admin role , but not be included in currentRoles，making > isUserAdmin() return false. > !image-2020-08-21-18-53-26-910.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-24055) Admin role do not have admin privilege when using hive client
[ https://issues.apache.org/jira/browse/HIVE-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongyixuan updated HIVE-24055: -- Attachment: image-2020-08-21-18-53-22-094.png > Admin role do not have admin privilege when using hive client > - > > Key: HIVE-24055 > URL: https://issues.apache.org/jira/browse/HIVE-24055 > Project: Hive > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: hive 2.3.2 > centos 7 >Reporter: gongyixuan >Priority: Critical > Attachments: image-2020-08-21-18-53-26-910.png > > > When judge a user is a admin role or not ，the currentRoles not initialized > correctly. > User zdp is admin role , but not be included in currentRoles，making > isUserAdmin() return false. > !image-2020-08-21-18-43-00-677.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-24055) Admin role do not have admin privilege when using hive client
[ https://issues.apache.org/jira/browse/HIVE-24055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongyixuan updated HIVE-24055: -- Attachment: (was: image-2020-08-21-18-38-20-692.png) > Admin role do not have admin privilege when using hive client > - > > Key: HIVE-24055 > URL: https://issues.apache.org/jira/browse/HIVE-24055 > Project: Hive > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: hive 2.3.2 > centos 7 >Reporter: gongyixuan >Priority: Critical > Attachments: image-2020-08-21-18-53-26-910.png > > > When judge a user is a admin role or not ，the currentRoles not initialized > correctly. > User zdp is admin role , but not be included in currentRoles，making > isUserAdmin() return false. > !image-2020-08-21-18-53-26-910.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HIVE-24051) Hive lineage information exposed in ExecuteWithHookContext
[ https://issues.apache.org/jira/browse/HIVE-24051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181770#comment-17181770 ] Szehon Ho commented on HIVE-24051: -- HI, [~chaosun] [~jxiang] would you guys help look at this small change? Thanks > Hive lineage information exposed in ExecuteWithHookContext > -- > > Key: HIVE-24051 > URL: https://issues.apache.org/jira/browse/HIVE-24051 > Project: Hive > Issue Type: Improvement > Components: Configuration >Reporter: Szehon Ho >Assignee: Szehon Ho >Priority: Major > Labels: pull-request-available > Attachments: HIVE-24051.patch > > Time Spent: 10m > Remaining Estimate: 0h > > The lineage information is not populated unless certain hooks are enabled. > However, this is a bit fragile, and no way for another hook that we write to > get this information. This proposes a flag to enable this instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HIVE-21753) Update HiveMetastore authorization to enable use of HiveAuthorizer implementation
[ https://issues.apache.org/jira/browse/HIVE-21753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181684#comment-17181684 ] Janus Chow commented on HIVE-21753: --- [~rmani] There is some problem in your latest patch file. The authEvent in L151 and L160 in HiveMetaStoreAuthorizer is not correct fro ALTER_TABLE and DROP_TABLE. > Update HiveMetastore authorization to enable use of HiveAuthorizer > implementation > - > > Key: HIVE-21753 > URL: https://issues.apache.org/jira/browse/HIVE-21753 > Project: Hive > Issue Type: Bug > Components: Hive >Affects Versions: 3.1.2 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Critical > Labels: pull-request-available > Fix For: 4.0.0 > > Attachments: HIVE-21753.1.patch, HIVE-21753.2.patch, > HIVE-21753.3.patch, HIVE-21753.4.patch, HIVE-21753.5.patch, > HIVE-21753.6.patch, HIVE-21753.7.patch > > Time Spent: 5h 50m > Remaining Estimate: 0h > > Currently HMS supports authorization using StorageBasedAuthorizationProvider > which relies on permissions at filesystem – like HDFS. Hive supports a > pluggable authorization interface, and multiple authorizer implementations > (like SQLStd, Ranger, Sentry) are available to authorizer access in Hive. > Extending HiveMetastore to use the same authorization interface as Hive will > enable use of pluggable authorization implementations; and will result in > consistent authorization across Hive, HMS and other services that use HMS > (like Spark). -- This message was sent by Atlassian Jira (v8.3.4#803005)
