[jira] [Commented] (HIVE-3009) do authorization for all metadata operations
[ https://issues.apache.org/jira/browse/HIVE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671826#comment-13671826 ] Vandana Ayyalasomayajula commented on HIVE-3009: [~mantonov]-- Yes, you are right. I could not pursue the patch further. If you or someone is interested, they can work on the jira. do authorization for all metadata operations Key: HIVE-3009 URL: https://issues.apache.org/jira/browse/HIVE-3009 Project: Hive Issue Type: Bug Components: Authorization, Metastore Reporter: Thejas M Nair Assignee: Vandana Ayyalasomayajula Most of the metadata read operations and some write operations are not checking for authorization. See org.apache.hadoop.hive.ql.plan.HiveOperation . Operations such as DESCTABLE and DROPDATABASE have null for required privileges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3009) do authorization for all metadata operations
[ https://issues.apache.org/jira/browse/HIVE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434449#comment-13434449 ] Vandana Ayyalasomayajula commented on HIVE-3009: Review Link: https://reviews.facebook.net/D4635 do authorization for all metadata operations Key: HIVE-3009 URL: https://issues.apache.org/jira/browse/HIVE-3009 Project: Hive Issue Type: Bug Components: Authorization, Metastore Reporter: Thejas M Nair Assignee: Vandana Ayyalasomayajula Most of the metadata read operations and some write operations are not checking for authorization. See org.apache.hadoop.hive.ql.plan.HiveOperation . Operations such as DESCTABLE and DROPDATABASE have null for required privileges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3377) ant model-jar command fails in metastore
Vandana Ayyalasomayajula created HIVE-3377: -- Summary: ant model-jar command fails in metastore Key: HIVE-3377 URL: https://issues.apache.org/jira/browse/HIVE-3377 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.10.0 Reporter: Vandana Ayyalasomayajula Priority: Minor Running ant model-jar command to set up eclipse dev environment from the following wiki: https://cwiki.apache.org/Hive/gettingstarted-eclipsesetup.html fails with the following message: BUILD FAILED **/workspace/hive-trunk/metastore/build.xml:22: The following error occurred while executing this line: **/workspace/hive-trunk/build-common.xml:112: Problem: failed to create task or type osfamily Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any presetdef/macrodef declarations have taken place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3009) do authorization for all metadata operations
[ https://issues.apache.org/jira/browse/HIVE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula reassigned HIVE-3009: -- Assignee: Vandana Ayyalasomayajula do authorization for all metadata operations Key: HIVE-3009 URL: https://issues.apache.org/jira/browse/HIVE-3009 Project: Hive Issue Type: Bug Components: Authorization, Metastore Reporter: Thejas M Nair Assignee: Vandana Ayyalasomayajula Most of the metadata read operations and some write operations are not checking for authorization. See org.apache.hadoop.hive.ql.plan.HiveOperation . Operations such as DESCTABLE and DROPDATABASE have null for required privileges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2542) DROP DATABASE CASCADE does not drop non-native tables.
[ https://issues.apache.org/jira/browse/HIVE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HIVE-2542: --- Attachment: HIVE-2542.07.patch DROP DATABASE CASCADE does not drop non-native tables. --- Key: HIVE-2542 URL: https://issues.apache.org/jira/browse/HIVE-2542 Project: Hive Issue Type: Bug Components: Metastore Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Labels: handler, hive, metastore, storage Attachments: HIVE-2542.04.patch, HIVE-2542.05.patch, HIVE-2542.06.patch, HIVE-2542.06.patch, HIVE-2542.07.patch, Hive-2542.03.patch, Hive-2542.patch The hive meta store client does not delete the non-native tables during the drop database dbname cascade operation. As a result even though the database is deleted the tables still exist. This is related to HCATALOG-144. A deeper look at the HiveMetaStoreClient's dropDatabase function, tells us that the function does not utilize the hive meta hooks of the tables in the database for dropping the non-native tables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2542) DROP DATABASE CASCADE does not drop non-native tables.
[ https://issues.apache.org/jira/browse/HIVE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278447#comment-13278447 ] Vandana Ayyalasomayajula commented on HIVE-2542: Hey Ashutosh, The arc diff does not seem to pick the moves correctly, so in addition to the above patch, you will have to execute the following commands while committing. mkdir hbase-handler/src/test/queries/positive svn add hbase-handler/src/test/queries/positive svn mv hbase-handler/src/test/queries/*.q hbase-handler/src/test/queries/positive/ svn mv hbase-handler/src/test/queries/*.m hbase-handler/src/test/queries/positive/ mkdir hbase-handler/src/test/results/positive svn add hbase-handler/src/test/results/positive svn mv hbase-handler/src/test/results/*.q.out hbase-handler/src/test/results/positive svn mv hbase-handler/src/test/results/*.m.out hbase-handler/src/test/results/positive ant test -Dtestcase=TestHBaseNegativeCliDriver ant test -Dtestcase=TestHBaseCliDriver commands run successfully. DROP DATABASE CASCADE does not drop non-native tables. --- Key: HIVE-2542 URL: https://issues.apache.org/jira/browse/HIVE-2542 Project: Hive Issue Type: Bug Components: Metastore Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Labels: handler, hive, metastore, storage Attachments: HIVE-2542.04.patch, HIVE-2542.05.patch, HIVE-2542.06.patch, HIVE-2542.06.patch, HIVE-2542.07.patch, Hive-2542.03.patch, Hive-2542.patch The hive meta store client does not delete the non-native tables during the drop database dbname cascade operation. As a result even though the database is deleted the tables still exist. This is related to HCATALOG-144. A deeper look at the HiveMetaStoreClient's dropDatabase function, tells us that the function does not utilize the hive meta hooks of the tables in the database for dropping the non-native tables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
