[jira] [Updated] (HIVE-3814) Cannot drop partitions on table when using Oracle metastore
[ https://issues.apache.org/jira/browse/HIVE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-3814: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 0.10. Thanks, Deepesh! > Cannot drop partitions on table when using Oracle metastore > --- > > Key: HIVE-3814 > URL: https://issues.apache.org/jira/browse/HIVE-3814 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0 > Environment: Oracle 11g r2 >Reporter: Deepesh Khandelwal >Assignee: Deepesh Khandelwal >Priority: Critical > Fix For: 0.10.0 > > Attachments: HIVE-3814.patch > > > Create a table with a partition. Try to drop the partition or the table > containing the partition. Following error is seen: > FAILED: Error in metadata: > MetaException(message:javax.jdo.JDODataStoreException: Error executing JDOQL > query "SELECT > 'org.apache.hadoop.hive.metastore.model.MPartitionColumnStatistics' AS > NUCLEUS_TYPE,THIS.AVG_COL_LEN,THIS."COLUMN_NAME",THIS.COLUMN_TYPE,THIS.DB_NAME,THIS.DOUBLE_HIGH_VALUE,THIS.DOUBLE_LOW_VALUE,THIS.LAST_ANALYZED,THIS.LONG_HIGH_VALUE,THIS.LONG_LOW_VALUE,THIS.MAX_COL_LEN,THIS.NUM_DISTINCTS,THIS.NUM_FALSES,THIS.NUM_NULLS,THIS.NUM_TRUES,THIS.PARTITION_NAME,THIS."TABLE_NAME",THIS.CS_ID > FROM PART_COL_STATS THIS LEFT OUTER JOIN PARTITIONS > THIS_PARTITION_PARTITION_NAME ON THIS.PART_ID = > THIS_PARTITION_PARTITION_NAME.PART_ID WHERE > THIS_PARTITION_PARTITION_NAME.PART_NAME = ? AND THIS.DB_NAME = ? AND > THIS."TABLE_NAME" = ?" : ORA-00904: "THIS"."PARTITION_NAME": invalid > identifier > The problem here is that the column "PARTITION_NAME" that the query is > referring to in table "PART_COL_STATS" is non-existent. Looking at the hive > schema scripts for mysql & derby, this should be "PARTITION_NAME". Postgres > also suffers from the same problem. -- 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-3814) Cannot drop partitions on table when using Oracle metastore
[ https://issues.apache.org/jira/browse/HIVE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-3814: --- Assignee: Deepesh Khandelwal > Cannot drop partitions on table when using Oracle metastore > --- > > Key: HIVE-3814 > URL: https://issues.apache.org/jira/browse/HIVE-3814 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0 > Environment: Oracle 11g r2 >Reporter: Deepesh Khandelwal >Assignee: Deepesh Khandelwal >Priority: Critical > Fix For: 0.10.0 > > Attachments: HIVE-3814.patch > > > Create a table with a partition. Try to drop the partition or the table > containing the partition. Following error is seen: > FAILED: Error in metadata: > MetaException(message:javax.jdo.JDODataStoreException: Error executing JDOQL > query "SELECT > 'org.apache.hadoop.hive.metastore.model.MPartitionColumnStatistics' AS > NUCLEUS_TYPE,THIS.AVG_COL_LEN,THIS."COLUMN_NAME",THIS.COLUMN_TYPE,THIS.DB_NAME,THIS.DOUBLE_HIGH_VALUE,THIS.DOUBLE_LOW_VALUE,THIS.LAST_ANALYZED,THIS.LONG_HIGH_VALUE,THIS.LONG_LOW_VALUE,THIS.MAX_COL_LEN,THIS.NUM_DISTINCTS,THIS.NUM_FALSES,THIS.NUM_NULLS,THIS.NUM_TRUES,THIS.PARTITION_NAME,THIS."TABLE_NAME",THIS.CS_ID > FROM PART_COL_STATS THIS LEFT OUTER JOIN PARTITIONS > THIS_PARTITION_PARTITION_NAME ON THIS.PART_ID = > THIS_PARTITION_PARTITION_NAME.PART_ID WHERE > THIS_PARTITION_PARTITION_NAME.PART_NAME = ? AND THIS.DB_NAME = ? AND > THIS."TABLE_NAME" = ?" : ORA-00904: "THIS"."PARTITION_NAME": invalid > identifier > The problem here is that the column "PARTITION_NAME" that the query is > referring to in table "PART_COL_STATS" is non-existent. Looking at the hive > schema scripts for mysql & derby, this should be "PARTITION_NAME". Postgres > also suffers from the same problem. -- 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-3814) Cannot drop partitions on table when using Oracle metastore
[ https://issues.apache.org/jira/browse/HIVE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepesh Khandelwal updated HIVE-3814: - Fix Version/s: 0.10.0 Status: Patch Available (was: Open) > Cannot drop partitions on table when using Oracle metastore > --- > > Key: HIVE-3814 > URL: https://issues.apache.org/jira/browse/HIVE-3814 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0 > Environment: Oracle 11g r2 >Reporter: Deepesh Khandelwal >Priority: Critical > Fix For: 0.10.0 > > Attachments: HIVE-3814.patch > > > Create a table with a partition. Try to drop the partition or the table > containing the partition. Following error is seen: > FAILED: Error in metadata: > MetaException(message:javax.jdo.JDODataStoreException: Error executing JDOQL > query "SELECT > 'org.apache.hadoop.hive.metastore.model.MPartitionColumnStatistics' AS > NUCLEUS_TYPE,THIS.AVG_COL_LEN,THIS."COLUMN_NAME",THIS.COLUMN_TYPE,THIS.DB_NAME,THIS.DOUBLE_HIGH_VALUE,THIS.DOUBLE_LOW_VALUE,THIS.LAST_ANALYZED,THIS.LONG_HIGH_VALUE,THIS.LONG_LOW_VALUE,THIS.MAX_COL_LEN,THIS.NUM_DISTINCTS,THIS.NUM_FALSES,THIS.NUM_NULLS,THIS.NUM_TRUES,THIS.PARTITION_NAME,THIS."TABLE_NAME",THIS.CS_ID > FROM PART_COL_STATS THIS LEFT OUTER JOIN PARTITIONS > THIS_PARTITION_PARTITION_NAME ON THIS.PART_ID = > THIS_PARTITION_PARTITION_NAME.PART_ID WHERE > THIS_PARTITION_PARTITION_NAME.PART_NAME = ? AND THIS.DB_NAME = ? AND > THIS."TABLE_NAME" = ?" : ORA-00904: "THIS"."PARTITION_NAME": invalid > identifier > The problem here is that the column "PARTITION_NAME" that the query is > referring to in table "PART_COL_STATS" is non-existent. Looking at the hive > schema scripts for mysql & derby, this should be "PARTITION_NAME". Postgres > also suffers from the same problem. -- 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-3814) Cannot drop partitions on table when using Oracle metastore
[ https://issues.apache.org/jira/browse/HIVE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepesh Khandelwal updated HIVE-3814: - Attachment: HIVE-3814.patch Attaching a patch that fixes the issue. > Cannot drop partitions on table when using Oracle metastore > --- > > Key: HIVE-3814 > URL: https://issues.apache.org/jira/browse/HIVE-3814 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0 > Environment: Oracle 11g r2 >Reporter: Deepesh Khandelwal >Priority: Critical > Attachments: HIVE-3814.patch > > > Create a table with a partition. Try to drop the partition or the table > containing the partition. Following error is seen: > FAILED: Error in metadata: > MetaException(message:javax.jdo.JDODataStoreException: Error executing JDOQL > query "SELECT > 'org.apache.hadoop.hive.metastore.model.MPartitionColumnStatistics' AS > NUCLEUS_TYPE,THIS.AVG_COL_LEN,THIS."COLUMN_NAME",THIS.COLUMN_TYPE,THIS.DB_NAME,THIS.DOUBLE_HIGH_VALUE,THIS.DOUBLE_LOW_VALUE,THIS.LAST_ANALYZED,THIS.LONG_HIGH_VALUE,THIS.LONG_LOW_VALUE,THIS.MAX_COL_LEN,THIS.NUM_DISTINCTS,THIS.NUM_FALSES,THIS.NUM_NULLS,THIS.NUM_TRUES,THIS.PARTITION_NAME,THIS."TABLE_NAME",THIS.CS_ID > FROM PART_COL_STATS THIS LEFT OUTER JOIN PARTITIONS > THIS_PARTITION_PARTITION_NAME ON THIS.PART_ID = > THIS_PARTITION_PARTITION_NAME.PART_ID WHERE > THIS_PARTITION_PARTITION_NAME.PART_NAME = ? AND THIS.DB_NAME = ? AND > THIS."TABLE_NAME" = ?" : ORA-00904: "THIS"."PARTITION_NAME": invalid > identifier > The problem here is that the column "PARTITION_NAME" that the query is > referring to in table "PART_COL_STATS" is non-existent. Looking at the hive > schema scripts for mysql & derby, this should be "PARTITION_NAME". Postgres > also suffers from the same problem. -- 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
