[jira] Commented: (HIVE-675) add database/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915946#action_12915946 ] Ning Zhang commented on HIVE-675: - Hi Carl, Branch 0.6 currently is broken when running a unit test. The error is as follows: compile-test: [javac] /data/users/nzhang/reviews/0.6/branch-0.6/build-common.xml:307: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 4 source files to /data/users/nzhang/reviews/0.6/branch-0.6/build/metastore/test/classes [javac] /data/users/nzhang/reviews/0.6/branch-0.6/metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java:76: partitionTester(org.apache.hadoop.hive.metastore.HiveMetaStoreClient,org.apache.hadoop.hive.conf.HiveConf) in org.apache.hadoop.hive.metastore.TestHiveMetaStore cannot be applied to (org.apache.hadoop.hive.metastore.HiveMetaStoreClient,org.apache.hadoop.hive.conf.HiveConf,boolean) [javac] TestHiveMetaStore.partitionTester(client, hiveConf, true); [javac] ^ [javac] 1 error It seems the last patch that touches TestHiveMetaStore and TestHiveMetaStoreRemote is this patch. Can you take a look? add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675-backport-v6.1.patch.txt, HIVE-675-backport-v6.2.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915961#action_12915961 ] Carl Steinbach commented on HIVE-675: - Hi Ning, I'm looking into it. add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675-backport-v6.1.patch.txt, HIVE-675-backport-v6.2.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915986#action_12915986 ] Carl Steinbach commented on HIVE-675: - @Ning: Can you please delete metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java? In the backport patch this file is deleted and replaced with TestRemoteHiveMetaStore.java, but it looks like for some reason this file was not actually deleted when the patch was applied. add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675-backport-v6.1.patch.txt, HIVE-675-backport-v6.2.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915990#action_12915990 ] Ning Zhang commented on HIVE-675: - That works. Thanks Carl! add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675-backport-v6.1.patch.txt, HIVE-675-backport-v6.2.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12910020#action_12910020 ] Namit Jain commented on HIVE-675: - I have take a look add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675-backport-v6.1.patch.txt, HIVE-675-backport-v6.2.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909496#action_12909496 ] John Sichi commented on HIVE-675: - I think it's fine to squash in this case. add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675-backport-v6.1.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12907048#action_12907048
]
Carl Steinbach commented on HIVE-675:
-
@Paul: No, not yet, but I think the following script should work:
{code}
ALTER TABLE DBS MODIFY DESC VARCHAR(4000);
ALTER TABLE DBS ADD COLUMN DB_LOCATION_URI VARCHAR(4000);
{code}
add database/schema 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-08-16.patch.txt,
HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt,
HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt,
HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904341#action_12904341 ] John Sichi commented on HIVE-675: - The metastore thrift API change is a breaking change, so we should either add another a patch which restores backwards-compatibility, or else mention this in the release notes. add database/schema 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.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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904364#action_12904364
]
Carl Steinbach commented on HIVE-675:
-
@John: Are you referring to the changes I made to
create_database/get_database/get_databases/drop_database in
hive_metastore.thrift?
In that file I replaced
{{liststring get_databases() throws(1:MetaException o1)}}
with
{{liststring get_databases(1:string pattern) throws(1:MetaException o1)}}
I can easily revert this change, but want to know if there are are other things
you think I need to fix.
I think the changes I made to create_database and drop_database should not be
an issue since these calls weren't actually supported in previous versions.
add database/schema 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.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-08-16.patch.txt,
HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt,
HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt,
HIVE-675.13.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/schema support Hive QL
[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904380#action_12904380
]
John Sichi commented on HIVE-675:
-
Oops, I misspoke; actually the thrift API is fine, it's the removal/change of
some methods from Java interface IMetaStoreClient which broke dependencies.
{noformat}
- public void dropTable(String tableName, boolean deleteData)
- throws MetaException, UnknownTableException, TException,
- NoSuchObjectException;
- public boolean tableExists(String tableName) throws MetaException,
+ public boolean tableExists(String databaseName, String tableName) throws
MetaException,
TException, UnknownDBException;
- public Table getTable(String tableName) throws MetaException, TException,
- NoSuchObjectException;
{noformat}
add database/schema 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.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-08-16.patch.txt,
HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt,
HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt,
HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904383#action_12904383 ] John Sichi commented on HIVE-675: - Ning hit the broken dependencies; he may be able to tell whether this list is complete. add database/schema 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.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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904388#action_12904388
]
Carl Steinbach commented on HIVE-675:
-
I removed these methods since they implicitly target the {{default}} database.
I can put them
back with a deprecation warning, but I also want to point out that old code
that depends on
these methods is probably no longer correct now that Hive supports multiple
databases.
Removing these methods entirely may be the easiest way to help people find
these errors.
add database/schema 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.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-08-16.patch.txt,
HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt,
HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt,
HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904392#action_12904392 ] John Sichi commented on HIVE-675: - Going through a deprecation phase helps ease transitions in deployment environments (like Facebook's) where not all upgrades can be done in lockstep. add database/schema 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.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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904415#action_12904415 ] Ning Zhang commented on HIVE-675: - @Carl, I got compiling errors for tableExists() and getTable(). It would be nice to bring back those methods (as well as other methods like dropTable) without the database argument. Putting deprecation warning is fine for me. add database/schema 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.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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904420#action_12904420 ] Carl Steinbach commented on HIVE-675: - @Ning: I filed HIVE-1607. Patch to follow shortly. Sorry for inconvenience. add database/schema 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.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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903082#action_12903082
]
Carl Steinbach commented on HIVE-675:
-
Cited the wrong lines from the patch. Here are the correct ones:
{noformat}
...
diff --git
metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java
metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java
deleted file mode 100644
index bc950b9..000
---
metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java
+++ /dev/null
...
{noformat}
add database/schema 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-08-16.patch.txt,
HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt,
HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt,
HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903180#action_12903180 ] Namit Jain commented on HIVE-675: - My bad in applying the patch - running tests again add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902581#action_12902581 ] Namit Jain commented on HIVE-675: - I will take a look again - Also, I think you would also like to have in 0.6 branch ? In that case, can you also prepare a patch for 0.6 add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902636#action_12902636 ] Carl Steinbach commented on HIVE-675: - That's correct. I will start work on the backport patch after this gets committed to trunk. add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt, HIVE-675.13.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902027#action_12902027 ] Namit Jain commented on HIVE-675: - Carl, The changes look good, but can you regenerate the patch ? I am getting some conflicts on trunk. add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902041#action_12902041 ] Carl Steinbach commented on HIVE-675: - Namit, will do. add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902069#action_12902069 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com bq. On 2010-08-17 15:32:59, namit jain wrote: bq. metastore/src/model/package.jdo, line 14 bq. http://review.cloudera.org/r/508/diff/4/?file=7227#file7227line14 bq. bq. Why do you want to change the field name ? I changed it since this refers to the value of the COMMENT clause in the CREATE DATABASE statement. I changed it back to the original value just to keep things simple. - Carl --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review934 --- add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902075#action_12902075 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/ --- (Updated 2010-08-24 13:55:16.686174) Review request for Hive Developers. Changes --- HIVE-675.12.patch.txt: * Added HiveMetaStore.getAllTables(String dbName) and HiveMetaStore.getAllDatabases() * Added ORDER BY clause to ObjectStore.getDatabases() * Reverted Database.getComment() to Database.getDescription() * Replaced a couple more hardcoded references to DEFAULT_DATABASE_NAME 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 (updated) - .gitignore 376cdc6 build-common.xml 00aa470 eclipse-templates/TestCliDriver.launchtemplate c304161 eclipse-templates/TestEmbeddedHiveMetaStore.launchtemplate PRE-CREATION eclipse-templates/TestHive.launchtemplate 24efc12 eclipse-templates/TestHiveMetaStoreChecker.launchtemplate PRE-CREATION eclipse-templates/TestRemoteHiveMetaStore.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/TestEmbeddedHiveMetaStore.java PRE-CREATION metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStore.java fff6aad metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java bc950b9 metastore/src/test/org/apache/hadoop/hive/metastore/TestRemoteHiveMetaStore.java PRE-CREATION ql/src/java/org/apache/hadoop/hive/ql/exec/DDLTask.java 28b4d2a ql/src/java/org/apache/hadoop/hive/ql/exec/MoveTask.java d59f48c ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java ce5d903 ql/src/java/org/apache/hadoop/hive/ql/metadata/Table.java 352af89 ql/src/java/org/apache/hadoop/hive/ql/parse/BaseSemanticAnalyzer.java eedf9e3 ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java 658eea5 ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g fca7ff6 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java cba4a66 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzerFactory.java 881290c ql/src/java/org/apache/hadoop/hive/ql/plan/CreateDatabaseDesc.java PRE-CREATION ql/src/java/org/apache/hadoop/hive/ql/plan/DDLWork.java 0c848e6 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 70d64ef ql/src/test/org/apache/hadoop/hive/ql/hooks/EnforceReadOnlyTables.java 8cff958 ql/src/test/org/apache/hadoop/hive/ql/metadata/TestHive.java ab39ca4
[jira] Commented: (HIVE-675) add database/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902081#action_12902081 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com bq. On 2010-08-24 14:23:09, Ted Yu wrote: bq. metastore/src/model/package.jdo, line 15 bq. http://review.cloudera.org/r/508/diff/4/?file=7227#file7227line15 bq. bq. name= should be changed as well. DESC is the name of a column that already exists in the schema. The name is not optimal, but changing it presents a bigger inconvenience. - Carl --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review1024 --- add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902083#action_12902083 ] HBase Review Board commented on HIVE-675: - Message from: Ted Yu ted...@yahoo.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review1024 --- metastore/src/model/package.jdo http://review.cloudera.org/r/508/#comment3249 name= should be changed as well. - Ted add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902099#action_12902099 ] Namit Jain commented on HIVE-675: - +1 will commit if tests pass. Needs support to lock the database, but will file a follow-up for that add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902275#action_12902275 ] Namit Jain commented on HIVE-675: - The following tests failed (TestCliDriver): rename_column.q database.q alter1.q alter2.q alter3.q Can you run the tests again ? add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899627#action_12899627 ] Namit Jain commented on HIVE-675: - Added comments at http://review.cloudera.org/r/508/diff Also, inputs and outputs need to be populated for 'drop database ..' It should consist of all the tables/partitions in that database. It is fine if you want to do so in a follow-up, in which case, please file a dependent jira add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899635#action_12899635 ] HBase Review Board commented on HIVE-675: - Message from: namit jain nj...@facebook.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review934 --- metastore/src/model/package.jdo http://review.cloudera.org/r/508/#comment3080 Why do you want to change the field name ? - namit add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899641#action_12899641 ] Namit Jain commented on HIVE-675: - Also, can you update the patch ? I am getting some conflicts after https://issues.apache.org/jira/browse/HIVE-1548 add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899642#action_12899642 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com bq. On 2010-08-11 06:57:04, namit jain wrote: bq. metastore/if/hive_metastore.thrift, line 35 bq. http://review.cloudera.org/r/508/diff/2/?file=5171#file5171line35 bq. bq. Same as John's earlier comment - do we need bq. to change the name. bq. bq. No-one is using this table in the metastore currently, bq. so it might be OK - but not sure, how JDO would bq. handle renaming a column Done. bq. On 2010-08-11 06:57:04, namit jain wrote: bq. ql/src/test/queries/clientpositive/database.q, line 15 bq. http://review.cloudera.org/r/508/diff/2/?file=5216#file5216line15 bq. bq. also add a test for 'show databases for a pattern' Done. - Carl --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review838 --- add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898830#action_12898830 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/ --- (Updated 2010-08-16 02:05:39.708868) Review request for Hive Developers. Changes --- Updated diff with https://issues.apache.org/jira/secure/attachment/12419726/hive-675-2009-9-16.patch 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 (updated) - .gitignore 376cdc6 build-common.xml d4ff895 eclipse-templates/TestEmbeddedHiveMetaStore.launchtemplate PRE-CREATION eclipse-templates/TestHive.launchtemplate 24efc12 eclipse-templates/TestRemoteHiveMetaStore.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/TestEmbeddedHiveMetaStore.java PRE-CREATION metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStore.java fff6aad metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java bc950b9 metastore/src/test/org/apache/hadoop/hive/metastore/TestRemoteHiveMetaStore.java PRE-CREATION ql/src/java/org/apache/hadoop/hive/ql/exec/DDLTask.java ef1da6b ql/src/java/org/apache/hadoop/hive/ql/exec/MoveTask.java d59f48c ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java e0761fc ql/src/java/org/apache/hadoop/hive/ql/metadata/Table.java 3300e2a ql/src/java/org/apache/hadoop/hive/ql/parse/BaseSemanticAnalyzer.java eedf9e3 ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java 1801c10 ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g b080780 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 682a8b5 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzerFactory.java 6af3b17 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/database_create_already_exists.q PRE-CREATION ql/src/test/queries/clientnegative/database_create_invalid_name.q PRE-CREATION ql/src/test/queries/clientnegative/database_drop_does_not_exist.q PRE-CREATION ql/src/test/queries/clientnegative/database_drop_not_empty.q PRE-CREATION
[jira] Commented: (HIVE-675) add database/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899070#action_12899070 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com bq. On 2010-08-09 15:51:55, John Sichi wrote: bq. metastore/src/model/package.jdo, line 11 bq. http://review.cloudera.org/r/508/diff/2/?file=5193#file5193line11 bq. bq. Do we really need to change this column name? I can see that it doesn't follow the conventions for other tables, but it might make upgrades a pain. bq. I reverted the change. bq. On 2010-08-09 15:51:55, John Sichi wrote: bq. ql/src/java/org/apache/hadoop/hive/ql/plan/ShowDatabasesDesc.java, line 41 bq. http://review.cloudera.org/r/508/diff/2/?file=5209#file5209line41 bq. bq. Should this be db_name instead of tab_name? Changed. - Carl --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review778 --- add database/schema 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-08-16.patch.txt, HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt, HIVE-675.10.patch.txt, HIVE-675.11.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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899073#action_12899073 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/ --- (Updated 2010-08-16 13:00:54.438322) Review request for Hive Developers. Changes --- * Fixed several eclipse launch configurations. * Refactored TestHiveMetaStore into TestEmbeddedHiveMetaStore and TestRemoteHiveMetaStore * Added a bunch of testcases. 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 (updated) - .gitignore 376cdc6 build-common.xml d4ff895 eclipse-templates/TestCliDriver.launchtemplate c304161 eclipse-templates/TestEmbeddedHiveMetaStore.launchtemplate PRE-CREATION eclipse-templates/TestHive.launchtemplate 24efc12 eclipse-templates/TestHiveMetaStoreChecker.launchtemplate PRE-CREATION eclipse-templates/TestRemoteHiveMetaStore.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/TestEmbeddedHiveMetaStore.java PRE-CREATION metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStore.java fff6aad metastore/src/test/org/apache/hadoop/hive/metastore/TestHiveMetaStoreRemote.java bc950b9 metastore/src/test/org/apache/hadoop/hive/metastore/TestRemoteHiveMetaStore.java PRE-CREATION ql/src/java/org/apache/hadoop/hive/ql/exec/DDLTask.java ef1da6b ql/src/java/org/apache/hadoop/hive/ql/exec/MoveTask.java d59f48c ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java e0761fc ql/src/java/org/apache/hadoop/hive/ql/metadata/Table.java 3300e2a ql/src/java/org/apache/hadoop/hive/ql/parse/BaseSemanticAnalyzer.java eedf9e3 ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java 1801c10 ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g b080780 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 682a8b5 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzerFactory.java 6af3b17 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/database_create_already_exists.q PRE-CREATION ql/src/test/queries/clientnegative/database_create_invalid_name.q PRE-CREATION
[jira] Commented: (HIVE-675) add database/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12897625#action_12897625 ] HBase Review Board commented on HIVE-675: - Message from: Carl Steinbach c...@cloudera.com bq. On 2010-08-11 06:57:04, namit jain wrote: bq. ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g, line 572 bq. http://review.cloudera.org/r/508/diff/2/?file=5203#file5203line572 bq. bq. remove KW_SCHEMAS In MySQL SHOW SCHEMAS is a synonym for SHOW DATABASES as of version 5.0.2. I think the general convention in Hive is to mimic the behavior of MySQL. Please let me know if there is a reason why we should not do that here. http://dev.mysql.com/doc/refman/5.0/en/show-databases.html - Carl --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review838 --- add database/schema 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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12897272#action_12897272 ] Namit Jain commented on HIVE-675: - comments posted on http://review.cloudera.org/r/508/diff add database/schema 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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12897275#action_12897275 ] HBase Review Board commented on HIVE-675: - Message from: namit jain nj...@facebook.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review838 --- metastore/if/hive_metastore.thrift http://review.cloudera.org/r/508/#comment2816 Same as John's earlier comment - do we need to change the name. No-one is using this table in the metastore currently, so it might be OK - but not sure, how JDO would handle renaming a column ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g http://review.cloudera.org/r/508/#comment2817 remove KW_SCHEMAS ql/src/test/queries/clientpositive/database.q http://review.cloudera.org/r/508/#comment2818 also add a test for 'show databases for a pattern' - namit add database/schema 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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896704#action_12896704 ] John Sichi commented on HIVE-675: - Any followup work needed here for HIVE-1126? add database/schema 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/schema support Hive QL
[ https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896725#action_12896725 ] HBase Review Board commented on HIVE-675: - Message from: John Sichi jsi...@facebook.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/508/#review778 --- metastore/src/model/package.jdo http://review.cloudera.org/r/508/#comment2660 Do we really need to change this column name? I can see that it doesn't follow the conventions for other tables, but it might make upgrades a pain. ql/src/java/org/apache/hadoop/hive/ql/plan/ShowDatabasesDesc.java http://review.cloudera.org/r/508/#comment2651 Should this be db_name instead of tab_name? - John add database/schema 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.
