[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-5264: -- Attachment: D12993.2.patch sershe updated the revision HIVE-5264 [jira] SQL generated by MetaStoreDirectSql.java not compliant with Postgres.. small rebase (conflict with other patch) Reviewers: ashutoshc, JIRA REVISION DETAIL https://reviews.facebook.net/D12993 CHANGE SINCE LAST DIFF https://reviews.facebook.net/D12993?vs=40107id=40443#toc AFFECTED FILES metastore/src/java/org/apache/hadoop/hive/metastore/MetaStoreDirectSql.java metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java To: JIRA, ashutoshc, sershe SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, D12993.2.patch, HIVE-5264.01.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Attachment: HIVE-5264.02.patch SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, D12993.2.patch, HIVE-5264.01.patch, HIVE-5264.02.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Status: Open (was: Patch Available) SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, D12993.2.patch, HIVE-5264.01.patch, HIVE-5264.02.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Status: Patch Available (was: Open) SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, D12993.2.patch, HIVE-5264.01.patch, HIVE-5264.02.patch, HIVE-5264.03.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Attachment: HIVE-5264.03.patch Exactly the same patch. Some random shamanic dancing to maybe appease HiveQA SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, D12993.2.patch, HIVE-5264.01.patch, HIVE-5264.02.patch, HIVE-5264.03.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-5264: --- Resolution: Fixed Fix Version/s: 0.13.0 Status: Resolved (was: Patch Available) Ran all tests locally. They passed. Committed to trunk. Thanks, Sergey! SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Fix For: 0.13.0 Attachments: D12993.1.patch, D12993.2.patch, HIVE-5264.01.patch, HIVE-5264.02.patch, HIVE-5264.03.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Status: Open (was: Patch Available) SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, HIVE-5264.01.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Status: Patch Available (was: Open) SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, HIVE-5264.01.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-5264: -- Attachment: D12993.1.patch sershe requested code review of HIVE-5264 [jira] SQL generated by MetaStoreDirectSql.java not compliant with Postgres.. Reviewers: JIRA Updating the patch. I've run TestCliDriver against pgsql and mysql and no queries fail do to the issues pertaining to this patch, other than because of HIVE-5304 (which also affects JDO and ordering). Some queries fail on postgres due to unrelated reasons (for example, non-ascii comments) also covered in HIVE-5304. TEST PLAN All tests; CLI test against MySQL and Postgres. REVISION DETAIL https://reviews.facebook.net/D12993 AFFECTED FILES metastore/src/java/org/apache/hadoop/hive/metastore/MetaStoreDirectSql.java metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java MANAGE HERALD RULES https://reviews.facebook.net/herald/view/differential/ WHY DID I GET THIS EMAIL? https://reviews.facebook.net/herald/transcript/31047/ To: JIRA, sershe SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Status: Patch Available (was: Open) SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Attachment: HIVE-5264.01.patch attach properly named patch for HiveQA SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: D12993.1.patch, HIVE-5264.01.patch, HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Attachment: HIVE-5264.patch preliminary patch, let me run the tests against different stores and then submit to Hive QA, there may be some bugs SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Attachments: HIVE-5264.patch Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5264) SQL generated by MetaStoreDirectSql.java not compliant with Postgres.
[ https://issues.apache.org/jira/browse/HIVE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-5264: --- Affects Version/s: (was: 0.11.0) 0.12.0 SQL generated by MetaStoreDirectSql.java not compliant with Postgres. - Key: HIVE-5264 URL: https://issues.apache.org/jira/browse/HIVE-5264 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.12.0 Environment: Ubuntu 12.04 PostgreSQL 9.1.8 Reporter: Alexander Behm Assignee: Sergey Shelukhin Some operations against the Hive Metastore seem broken against Postgres. For example, when using HiveMetastoreClient.listPartitions() the Postgres logs show queries such as: 2013-09-09 19:10:01 PDT STATEMENT: select PARTITIONS.PART_ID from PARTITIONS inner join TBLS on PARTITIONS.TBL_ID = TBLS.TBL_ID inner join DBS on TBLS.DB_ID = DBS.DB_ID where TBLS.TBL_NAME = $1 and DBS.NAME = $2 order by PART_NAME asc with a somewhat cryptic (but correct) error: ERROR: relation partitions does not exist at character 32 Postgres identifiers are somewhat unusual. Unquoted identifiers are interpreted as lower case (there is no Postgres option to change this). Since the Metastore table schema uses upper case table names, the correct SQL requires escaped identifiers to those tables, i.e., select PARTITIONS.PART_ID from PARTITIONS... Hive sets metastore.try.direct.sql=true by default, so the above SQL is generated by hive/metastore/MetaStoreDirectSql.java, i.e., this is not a Datanucleus problem. When I set metastore.try.direct.sql=false, then the Metastore backed by Postgres works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
