[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896688#action_12896688 ] John Sichi commented on HIVE-675: - I'm getting conflicts attempting to apply HIVE-675-2010-8-4.patch.txt on latest trunk. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Metastore, Query Processor >Reporter: Prasad Chakka >Assignee: Carl Steinbach > Fix For: 0.6.0, 0.7.0 > > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch, HIVE-675-2010-7-16.patch.txt, > HIVE-675-2010-8-4.patch.txt > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895507#action_12895507 ] Namit Jain commented on HIVE-675: - Thanks Carl, I will take a look > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Metastore, Query Processor >Reporter: Prasad Chakka >Assignee: Carl Steinbach > Fix For: 0.6.0, 0.7.0 > > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch, HIVE-675-2010-7-16.patch.txt, > HIVE-675-2010-8-4.patch.txt > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895457#action_12895457 ] HBase Review Board commented on HIVE-675: - Message from: "Carl Steinbach" --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/ --- Review request for Hive Developers. Summary --- Database/Scheme support for Hive. * Implemented 'SHOW DATABASES' command * Refactored TestHiveMetaStore and enabled tests for remote metastore client. * Added launch configurations for TestHiveMetaStore and TestHiveMetaStoreRemote This addresses bug HIVE-675. http://issues.apache.org/jira/browse/HIVE-675 Diffs - build-common.xml d4ff895 eclipse-templates/TestHive.launchtemplate 24efc12 eclipse-templates/TestHiveMetaStore.launchtemplate PRE-CREATION eclipse-templates/TestHiveMetaStoreRemote.launchtemplate PRE-CREATION metastore/if/hive_metastore.thrift 478d0af metastore/src/gen-cpp/ThriftHiveMetastore.h e2538fb metastore/src/gen-cpp/ThriftHiveMetastore.cpp f945a3a metastore/src/gen-cpp/ThriftHiveMetastore_server.skeleton.cpp ed2bb99 metastore/src/gen-cpp/hive_metastore_types.h 1b0c706 metastore/src/gen-cpp/hive_metastore_types.cpp b5a403d metastore/src/gen-javabean/org/apache/hadoop/hive/metastore/api/Database.java 78c78d9 metastore/src/gen-javabean/org/apache/hadoop/hive/metastore/api/ThriftHiveMetastore.java 25408d9 metastore/src/gen-php/ThriftHiveMetastore.php ea4add5 metastore/src/gen-php/hive_metastore_types.php 61872a0 metastore/src/gen-py/hive_metastore/ThriftHiveMetastore-remote fc06cba metastore/src/gen-py/hive_metastore/ThriftHiveMetastore.py 4a0bc67 metastore/src/gen-py/hive_metastore/ttypes.py ea7269e metastore/src/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java 39dbd52 metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java 4fb296a metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStoreClient.java c6541af metastore/src/java/org/apache/hadoop/hive/metastore/IMetaStoreClient.java 6013644 metastore/src/java/org/apache/hadoop/hive/metastore/MetaStoreUtils.java 0818689 metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java a06384c metastore/src/java/org/apache/hadoop/hive/metastore/RawStore.java 4951bd6 metastore/src/java/org/apache/hadoop/hive/metastore/Warehouse.java 4488f94 metastore/src/model/org/apache/hadoop/hive/metastore/model/MDatabase.java b3e098d metastore/src/model/package.jdo 206ba75 metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStore.java fff6aad metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreBase.java PRE-CREATION metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java bc950b9 ql/src/java/org/apache/hadoop/hive/ql/exec/DDLTask.java bc268a4 ql/src/java/org/apache/hadoop/hive/ql/exec/MoveTask.java d59f48c ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java 04dd9e3 ql/src/java/org/apache/hadoop/hive/ql/metadata/Table.java 2ecda01 ql/src/java/org/apache/hadoop/hive/ql/parse/BaseSemanticAnalyzer.java eedf9e3 ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java 0484c91 ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g 02bf926 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 70cd05f ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzerFactory.java eb079aa ql/src/java/org/apache/hadoop/hive/ql/plan/CreateDatabaseDesc.java PRE-CREATION ql/src/java/org/apache/hadoop/hive/ql/plan/DDLWork.java ed4ed22 ql/src/java/org/apache/hadoop/hive/ql/plan/DropDatabaseDesc.java PRE-CREATION ql/src/java/org/apache/hadoop/hive/ql/plan/ShowDatabasesDesc.java PRE-CREATION ql/src/java/org/apache/hadoop/hive/ql/plan/SwitchDatabaseDesc.java PRE-CREATION ql/src/test/org/apache/hadoop/hive/ql/QTestUtil.java b4651a2 ql/src/test/org/apache/hadoop/hive/ql/metadata/TestHive.java ab39ca4 ql/src/test/org/apache/hadoop/hive/ql/metadata/TestHiveMetaStoreChecker.java 26cc71a ql/src/test/queries/clientnegative/create_database_bad_name.q PRE-CREATION ql/src/test/queries/clientnegative/database_switch_test.q PRE-CREATION ql/src/test/queries/clientpositive/database.q PRE-CREATION ql/src/test/results/clientnegative/create_database_bad_name.q.out PRE-CREATION ql/src/test/results/clientnegative/database_switch_test.q.out PRE-CREATION ql/src/test/results/clientpositive/database.q.out PRE-CREATION Diff: http://review.cloudera.org/r/508/diff Testing --- Thanks, Carl > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jir
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888009#action_12888009 ] Carl Steinbach commented on HIVE-675: - @Pradeep: I'm almost done with this. Will post an updated patch soon. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Metastore, Query Processor >Reporter: Prasad Chakka >Assignee: Carl Steinbach > Fix For: 0.6.0, 0.7.0 > > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887995#action_12887995 ] Pradeep Kamath commented on HIVE-675: - Any updates on this patch? The last one was in May - any chance this will be committed soon or are there outstanding issues? > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Metastore, Query Processor >Reporter: Prasad Chakka >Assignee: Carl Steinbach > Fix For: 0.6.0, 0.7.0 > > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869086#action_12869086 ] Carl Steinbach commented on HIVE-675: - I'm in the middle of updating this patch and plan to post the result in the next day. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: Carl Steinbach > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844706#action_12844706 ] Alex Loddengaard commented on HIVE-675: --- Hi guys, Any updates here? Would be great to have this patch committed! Thanks, Alex > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797486#action_12797486 ] Alex Loddengaard commented on HIVE-675: --- I will be out of the office Thursday, 1/7, through Wednesday, 1/13, back in the office Thursday, 1/14. I will be checking email fairly consistently in the evenings. Please contact Christophe Bisciglia (christo...@cloudera.com) with any support or training emergencies. Otherwise, you'll hear from me soon. Thanks, Alex > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797477#action_12797477 ] Zheng Shao commented on HIVE-675: - Yongqiang, you can start adapt the patch to trunk right now. The plan is to branch 0.5 on 1/7/2010 (tomorrow). After that we can quickly review this diff and get it in. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797238#action_12797238 ] He Yongqiang commented on HIVE-675: --- Hi Jeff, Sorry for the delay. Actually it is now holding for the release of 0.5 because it has many related jiras. Let's commit this after the release of 0.5. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797225#action_12797225 ] Jeff Hammerbacher commented on HIVE-675: Hey, Is this patch in a state where it could go into 0.5? If it's not going to be polished off, please let us know. Thanks, Jeff > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778219#action_12778219 ] He Yongqiang commented on HIVE-675: --- Hey Jeff, Sorry, i just saw your comments. And sorry for missing your earlier comment. The patch was ready to commit, only need a testcase. But i am sure it need to be adjust to trunk code. I will work out a new version soon. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778198#action_12778198 ] Jeff Hammerbacher commented on HIVE-675: Ping. Any chance this patch can be cleaned up and committed to trunk soon? > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768991#action_12768991 ] Jeff Hammerbacher commented on HIVE-675: Hey Yongqiang, What's the status of this patch? Thanks, Jeff > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758265#action_12758265 ] He Yongqiang commented on HIVE-675: --- Sorry, the "FAILED: Unknown exception : null" will be adressed in a new diff. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758263#action_12758263 ] He Yongqiang commented on HIVE-675: --- >>Do you want to check for the existence of the location while creating a >>database - do we want to throw an error if it already exists. Currently, it will not throw any error if the database dir is already there. I think this is the same as creating table. And i always do "drop table" and "create table" stuff, and i can switch machines, and only need to redo the "create table ..." and the data is available. I think this is very useful. >>in create_db_bad_location, can you throw a more meaningful error - location >>is bad or something like that Actually i already throw an exception with msg "Database location must be an absolute URI.". But i think the error msg "FAILED: Unknown exception : null" is not unique to this, and i think it has been reported somewhere in mailist or a jira page. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757985#action_12757985 ] Namit Jain commented on HIVE-675: - Also, in create_db_bad_location, can you throw a more meaningful error -- location is bad or something like that > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757982#action_12757982 ] Namit Jain commented on HIVE-675: - The changes look good - I am running tests right now. I just add 1 minor comment: Do you want to check for the existence of the location while creating a database - do we want to throw an error if it already exists. This applies to both default and user-specified location. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-21.patch, hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757767#action_12757767 ] Prasad Chakka commented on HIVE-675: What is the reason for not using a default path (/dbname) if location argument is null? It is possible that tools other than Hive CLI can create databases and they don't necessarily know what is the default path should be. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, > hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757588#action_12757588 ] Namit Jain commented on HIVE-675: - Mostly looks good, I had some minor comments: 1. No positive test for CREATE DATEBASE 2. Instead of having a separate processor, it might be a good idea to support 'use database' in Hive.g - in general, we are trying to add everything to Hive.g, since it will make adding different clients easy. 3. More positive tests - the test that you mentioned in the beginning - insert into db2 while selecting from db1 - 4. database_test.q and database_switch_test.q seem to be the same. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755888#action_12755888 ] Prasad Chakka commented on HIVE-675: Yeah, i never meant to fix this in this JIRA. just saying that we might need it in the future. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-7.patch, > hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755879#action_12755879 ] Zheng Shao commented on HIVE-675: - I think moving SessionState is a separate issue. The current database is part of Hive.java, so this issue does not depend on moving SessionState. We can discuss when and how to move SessionState in a separate jira. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755384#action_12755384 ] He Yongqiang commented on HIVE-675: --- There are two classes SessionState refers may block moving SessionState from ql to common, Utilities and HiveHistory. For Utilities, we can split it and add another Utilites to common package. But it is not easy for HiveHistory, it refers to QueryPlan and Task, which then refer to many others... So i think this would need a refactory of packing? > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754372#action_12754372 ] Prasad Chakka commented on HIVE-675: There is no way to refer to SessionState from inside of hive.ql.metadata or hive.metadata. I think this problem is going to bite us. We may need to access Session context from all over the package so we need to put all this information in Common which is accessible to all. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753897#action_12753897 ] He Yongqiang commented on HIVE-675: --- >>if approach A for HIVE-584 is chosen then shouldn't the current patch work >>without any changes? yes, it will work without changes. But Hive is now a thread local obj itself, so just as Zheng said, we don't need to protect the current database with another level of ThreadLocal. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753675#action_12753675 ] Prasad Chakka commented on HIVE-675: wait, if approach A for HIVE-584 is chosen then shouldn't the current patch work without any changes? > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753520#action_12753520 ] He Yongqiang commented on HIVE-675: --- Talked offline with Zheng, will upload a new fix when hive-584 committed. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753396#action_12753396
]
He Yongqiang commented on HIVE-675:
---
>>Assuming Hive is an inner field of SessionState, we don't need to protect the
>>current database with another level of ThreadLocal.
yes. hive is a singleton object.
{noformat}
public class Hive {
static final private Log LOG = LogFactory.getLog("hive.ql.metadata.Hive");
static Hive db = null;
.
public static Hive get(HiveConf c, boolean needsRefresh) throws HiveException
{
if(db == null || needsRefresh) {
closeCurrent();
c.set("fs.scheme.class","dfs");
db = new Hive(c);
}
return db;
}
{noformat}
So even though Hive is an inner field of SessionState, but i think they all
refer to the singleton instance at runtime. So we need to make the current
database be a ThreadLocal variable.
> add database/scheme support Hive QL
> ---
>
> Key: HIVE-675
> URL: https://issues.apache.org/jira/browse/HIVE-675
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
>Reporter: Prasad Chakka
>Assignee: He Yongqiang
> Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch
>
>
> Currently all Hive tables reside in single namespace (default). Hive should
> support multiple namespaces (databases or schemas) such that users can create
> tables in their specific namespaces. These name spaces can have different
> warehouse directories (with a default naming scheme) and possibly different
> properties.
> There is already some support for this in metastore but Hive query parser
> should have this feature as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753246#action_12753246 ] Zheng Shao commented on HIVE-675: - I see. Assuming Hive is an inner field of SessionState, we don't need to protect the current database with another level of ThreadLocal. Thoughts? > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753245#action_12753245 ] He Yongqiang commented on HIVE-675: --- is hive always used with a SessionState? I think hive is an inner field of SessionState, so it maybe not good to call its container(parent session object) currentDatabase(). > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753208#action_12753208 ] Zheng Shao commented on HIVE-675: - Shall we put currentDatabase() into Session? We don't want another ThreadLocal variable. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753166#action_12753166 ] Prasad Chakka commented on HIVE-675: Yes, by default currentDatabase() can be used and since only Hive.java holds the current database name, it should be fine. otherwise patch looks good. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752904#action_12752904 ] He Yongqiang commented on HIVE-675: --- Prasad, when i am looking into deprecating methods in Hive, i think we may need to open a new jira to track that. Hive.java has its currentDatabase tracking which database is currently in use, so it's reasonable to have methods without dbName argument. And most of methods in Hive.java do not have a dbName argument, they will use the current db by default. Do we really need to add new methods with the dbname argument now? What do you think? > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752891#action_12752891 ] He Yongqiang commented on HIVE-675: --- >>MetaStoreUtils.DEFAULT_DATABASE_NAME is sometimes replaced with >>currentDatabase and sometimes left empty (in DDLTask.java) why? When empty in DDLTask, it will use getCurrentDatabase() as the dbName inside Hive. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752888#action_12752888 ] He Yongqiang commented on HIVE-675: --- >>i thought all Hive.java functions that do not take database name as argument >>are deprecated. yes. exactly. I was thinking to open a new jira to deprecate/remove them. I will make them deprecated in a new patch for this jira. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752884#action_12752884 ] Prasad Chakka commented on HIVE-675: MetaStoreUtils.DEFAULT_DATABASE_NAME is sometimes replaced with currentDatabase and sometimes left empty (in DDLTask.java) why? i thought all Hive.java functions that do not take database name as argument are deprecated. no? > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka >Assignee: He Yongqiang > Attachments: hive-675-2009-9-7.patch, hive-675-2009-9-8.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-675) add database/scheme support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752204#action_12752204 ] Prasad Chakka commented on HIVE-675: 1) more test clientpositive & clientnegative tests 2) db location should take an URI rather than a path. since location can point to a different HDFS instance 3) this path does not support ... If you are not planning to add that support then create a new JIRA. 4) there should be a way to easily move tbl from on db to another db. may be open a JIRA for that as well? 5) HiveMetaStore.java: if the given db location is not a proper URI then it is silently ignored and default path is being used. HiveMetastore should throw an error instead if the path is not absolute or a proper URI 6) remove ql/junit233767264.properties from patch 7) remove ql/junitvmwatcher1237844024.properties from patch 8) there are lot of other locations where MetaStoreUtils.DEFAULT_DATABASE_NAME is used. It should be replaced by Hive.currentDatabase 9) is Hive.currentDatabase thread-safe. does it work in HiveServer where multiple threads can each have separate currentDatabases? 10) Hive.createDatabase() & dropDatabase() should throw AlreadyExistsException() instead of throwin HiveException 11) rename isDatabaseExist() to databaseExists() 12) currentDatabase should either be in SessionState or Hive. There is no need for it to be stored in both objects. > add database/scheme support Hive QL > --- > > Key: HIVE-675 > URL: https://issues.apache.org/jira/browse/HIVE-675 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Prasad Chakka > Attachments: hive-675-2009-9-7.patch > > > Currently all Hive tables reside in single namespace (default). Hive should > support multiple namespaces (databases or schemas) such that users can create > tables in their specific namespaces. These name spaces can have different > warehouse directories (with a default naming scheme) and possibly different > properties. > There is already some support for this in metastore but Hive query parser > should have this feature as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
