[jira] [Created] (HIVE-2777) ability to add and drop partitions atomically

2012-02-04 Thread Aniket Mokashi (Created) (JIRA) 
ability to add and drop partitions atomically
-

 Key: HIVE-2777
 URL: https://issues.apache.org/jira/browse/HIVE-2777
 Project: Hive
  Issue Type: New Feature
  Components: Metastore
Reporter: Aniket Mokashi
 Fix For: 0.9.0


Hive should have ability to atomically add and drop partitions. This way admins 
can change partitions atomically without breaking the running jobs. It allows 
admin to merge several partitions into one.
Essentially, we would like to have an api- add_drop_partitions(String db, 
String tbl_name, ListPartition addParts, ListListString dropParts, 
boolean deleteData);
This jira covers changes required for metastore and thrift.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2702) listPartitionsByFilter only supports non-string partitions

2012-01-09 Thread Aniket Mokashi (Created) (JIRA) 
listPartitionsByFilter only supports non-string partitions
--

 Key: HIVE-2702
 URL: https://issues.apache.org/jira/browse/HIVE-2702
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.8.1
Reporter: Aniket Mokashi


listPartitionsByFilter supports only non-string partitions. This is because its 
explicitly specified in generateJDOFilterOverPartitions in ExpressionTree.java. 

//Can only support partitions whose types are string
  if( ! table.getPartitionKeys().get(partitionColumnIndex).
  
getType().equals(org.apache.hadoop.hive.serde.Constants.STRING_TYPE_NAME) ) {
throw new MetaException
(Filtering is supported only on partition keys of type string);
  }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2701) listPartitionsByFilter only supports non-string partitions

2012-01-09 Thread Aniket Mokashi (Created) (JIRA) 
listPartitionsByFilter only supports non-string partitions
--

 Key: HIVE-2701
 URL: https://issues.apache.org/jira/browse/HIVE-2701
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.8.1
Reporter: Aniket Mokashi


listPartitionsByFilter supports only non-string partitions. This is because its 
explicitly specified in generateJDOFilterOverPartitions in ExpressionTree.java. 

//Can only support partitions whose types are string
  if( ! table.getPartitionKeys().get(partitionColumnIndex).
  
getType().equals(org.apache.hadoop.hive.serde.Constants.STRING_TYPE_NAME) ) {
throw new MetaException
(Filtering is supported only on partition keys of type string);
  }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2617) Insert overwrite table db.tname fails if partition already exists

2011-11-30 Thread Aniket Mokashi (Created) (JIRA) 
Insert overwrite table db.tname fails if partition already exists 
--

 Key: HIVE-2617
 URL: https://issues.apache.org/jira/browse/HIVE-2617
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Reporter: Aniket Mokashi


Insert Overwrite table db.tname fails if partition already exists.
For example-
insert overwrite table db.tname PARTITION(part='p') select .. from t2 where 
part='p'; fails if partition 'p' already exists. Workaround is - use db; and 
the fire the command.
From the source code-
alterPartition(tbl.getTableName(), new Partition(tbl, tpart)); takes String 
tablename as argument and loses db information. Table table = 
newTable(tablename) is called to retrieve table from name. But, it relies on 
currentDatabase value (hence the workaround).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira