[jira] [Created] (HIVE-2581) explain task: getJSONPlan throws a NPE if the ast is null
explain task: getJSONPlan throws a NPE if the ast is null - Key: HIVE-2581 URL: https://issues.apache.org/jira/browse/HIVE-2581 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain -- 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-2595) add a table level property which does not let the table or any of its partitions to be dropped
add a table level property which does not let the table or any of its partitions to be dropped -- Key: HIVE-2595 URL: https://issues.apache.org/jira/browse/HIVE-2595 Project: Hive Issue Type: Improvement Reporter: Namit Jain The current approach: alter table enable no_drop; does not prevent the partitions from being dropped. This new property should prevent both the table and any of its partitions (current, future) from getting dropped. -- 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-2602) add support for insert partition overwrite(...) if not exists
add support for insert partition overwrite(...) if not exists - Key: HIVE-2602 URL: https://issues.apache.org/jira/browse/HIVE-2602 Project: Hive Issue Type: New Feature Reporter: Namit Jain INSERT OVERWRITE TABLE X PARTITION (a=b, c=d) IF NOT EXISTS ... The partition should be created and written if and only if it's not there already. The support can be added for dynamic partitions in the future, but this jira is for adding this support for static partitions. -- 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-2605) Setting no_drop on a table should cascade to child partitions
Setting no_drop on a table should cascade to child partitions - Key: HIVE-2605 URL: https://issues.apache.org/jira/browse/HIVE-2605 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain When NO_DROP is set on a table, it does not cascade to the partitions of the table. There should be an option to do so. -- 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-2632) ignore exception for external jars via reflection
ignore exception for external jars via reflection - Key: HIVE-2632 URL: https://issues.apache.org/jira/browse/HIVE-2632 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain -- 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-2634) revert HIVE-2566
revert HIVE-2566 Key: HIVE-2634 URL: https://issues.apache.org/jira/browse/HIVE-2634 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain This is leading to some problems. I will upload the offending testcase in a new jira. -- 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-2635) wrong class loader used for external jars
wrong class loader used for external jars - Key: HIVE-2635 URL: https://issues.apache.org/jira/browse/HIVE-2635 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain -- 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-2641) SkewJoin should report progress while writing skew keys to HDFS
SkewJoin should report progress while writing skew keys to HDFS --- Key: HIVE-2641 URL: https://issues.apache.org/jira/browse/HIVE-2641 Project: Hive Issue Type: Improvement Reporter: Namit Jain RowContainer.copyToDFSDirectory is used to write the skew keys to HDFS. But this can take a long time, and while it is happening, the MR framework does not see progress from the reducer. The code should do the copy in smaller unit and report progress to the MR framework -- 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-2651) The variable hive.exec.mode.local.auto.tasks.max should be changed
The variable hive.exec.mode.local.auto.tasks.max should be changed -- Key: HIVE-2651 URL: https://issues.apache.org/jira/browse/HIVE-2651 Project: Hive Issue Type: Improvement Reporter: Namit Jain It should be called hive.exec.mode.local.auto.files.max instead. The number of input files are checked currently. -- 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-2658) add a option in hive to skip corrupted data entirely
add a option in hive to skip corrupted data entirely Key: HIVE-2658 URL: https://issues.apache.org/jira/browse/HIVE-2658 Project: Hive Issue Type: New Feature Reporter: Namit Jain Assignee: He Yongqiang Add a new parameter: hive.skip.corrupted.data This is independent of the type of the underlying data. The idea is as follows: We have some corrupted data in our cluster right now. We will run hive over all the corrupted partitions: use bucketizedhiveinputformat set hive.skip.corrupted.data=true insert overwrite table partition select * from where This way, @ will be regenerated with all the data that can be read. If HiveRecordReader gets a exception getting the next row, the mapper will behave as if no more data is present in the file. -- 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-2668) Minor cleanup to HIVE-2642
Minor cleanup to HIVE-2642 -- Key: HIVE-2668 URL: https://issues.apache.org/jira/browse/HIVE-2668 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: He Yongqiang INLINE COMMENTS ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMRProcContext.java:105 can you add some comments here ? This is not really the top operators - this contains the list of intermediate tables also. This code is difficult to debug later on, so more comments would be helpful Look at union22.q.out. map-join followed by union, an extra stage is introduced. We dont have to optimize this - just wanted to make sure it is intentional. 1 general comment about the new test union26.q - Reduce the test output, I mean, you dont need to load all 500 rows for this test. It makes the test output really difficult to review. ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMRUnion1.java:245 remove this comment -- 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-2669) remove special processing for map-join
remove special processing for map-join -- Key: HIVE-2669 URL: https://issues.apache.org/jira/browse/HIVE-2669 Project: Hive Issue Type: Improvement Reporter: Namit Jain With hive.auto.convert.join, there is no need for the user to specify map-join hint. It should be completely ignored, other than for bucketized join which can be cleaned later. There is a lot of code in the optimizer for processing union followed by map-join etc. which should be gotten rid of. -- 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-2769) union with a multi-table insert is not working
union with a multi-table insert is not working -- Key: HIVE-2769 URL: https://issues.apache.org/jira/browse/HIVE-2769 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain -- 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-2772) make union31.q deterministic
make union31.q deterministic Key: HIVE-2772 URL: https://issues.apache.org/jira/browse/HIVE-2772 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain Attachments: HIVE-2772.D1557.1.patch -- 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-2785) support use cluster
support use cluster --- Key: HIVE-2785 URL: https://issues.apache.org/jira/browse/HIVE-2785 Project: Hive Issue Type: New Feature Reporter: Namit Jain use cluster; use cluster ; should be supported -- 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-2786) Throw an error if the user tries to insert a table into a cluster other than the primary cluster
Throw an error if the user tries to insert a table into a cluster other than the primary cluster Key: HIVE-2786 URL: https://issues.apache.org/jira/browse/HIVE-2786 Project: Hive Issue Type: New Feature Reporter: Namit Jain By default, the user can only insert into the primary cluster. Add an option to insert into the secondary clusters also -- 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-2795) View partitions do not have a storage descriptor
View partitions do not have a storage descriptor Key: HIVE-2795 URL: https://issues.apache.org/jira/browse/HIVE-2795 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Kevin Wilfong -- 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-2798) add an option to change the primary region for a table
add an option to change the primary region for a table -- Key: HIVE-2798 URL: https://issues.apache.org/jira/browse/HIVE-2798 Project: Hive Issue Type: New Feature Reporter: Namit Jain Assignee: Namit Jain This should error out if any of the partitions are not present in the primary region -- 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-2799) change the following thrift apis to add a region
change the following thrift apis to add a region Key: HIVE-2799 URL: https://issues.apache.org/jira/browse/HIVE-2799 Project: Hive Issue Type: New Feature Reporter: Namit Jain Assignee: Namit Jain list get_tables(1: string db_name, 2: string pattern) throws (1: MetaException o1) list get_all_tables(1: string db_name) throws (1: MetaException o1) Table get_table(1:string dbname, 2:string tbl_name) throws (1:MetaException o1, 2:NoSuchObjectException o2) list get_table_objects_by_name(1:string dbname, 2:list tbl_names) throws (1:MetaException o1, 2:InvalidOperationException o2, 3:UnknownDBException o3) list get_table_names_by_filter(1:string dbname, 2:string filter, 3:i16 max_tables=-1) throws (1:MetaException o1, 2:InvalidOperationException o2, 3:UnknownDBException o3) Partition add_partition(1:Partition new_part) throws(1:InvalidObjectException o1, 2:AlreadyExistsException o2, 3:MetaException o3) i32 add_partitions(1:list new_parts) throws(1:InvalidObjectException o1, 2:AlreadyExistsException o2, 3:MetaException o3) Partition append_partition(1:string db_name, 2:string tbl_name, 3:list part_vals) throws (1:InvalidObjectException o1, 2:AlreadyExistsException o2, 3:MetaException o3) Partition append_partition_by_name(1:string db_name, 2:string tbl_name, 3:string part_name) throws (1:InvalidObjectException o1, 2:AlreadyExistsException o2, 3:MetaException o3) bool drop_partition(1:string db_name, 2:string tbl_name, 3:list part_vals, 4:bool deleteData) throws(1:NoSuchObjectException o1, 2:MetaException o2) bool drop_partition_by_name(1:string db_name, 2:string tbl_name, 3:string part_name, 4:bool deleteData) throws(1:NoSuchObjectException o1, 2:MetaException o2) Partition get_partition(1:string db_name, 2:string tbl_name, 3:list part_vals) throws(1:MetaException o1, 2:NoSuchObjectException o2) Partition get_partition_with_auth(1:string db_name, 2:string tbl_name, 3:list part_vals, 4: string user_name, 5: list group_names) throws(1:MetaException o1, 2:NoSuchObjectException o2) Partition get_partition_by_name(1:string db_name 2:string tbl_name, 3:string part_name) throws(1:MetaException o1, 2:NoSuchObjectException o2) list get_partitions(1:string db_name, 2:string tbl_name, 3:i16 max_parts=-1) throws(1:NoSuchObjectException o1, 2:MetaException o2) list get_partitions_with_auth(1:string db_name, 2:string tbl_name, 3:i16 max_parts=-1, 4: string user_name, 5: list group_names) throws(1:NoSuchObjectException o1, 2:MetaException o2) list get_partition_names(1:string db_name, 2:string tbl_name, 3:i16 max_parts=-1) throws(1:MetaException o2) list get_partitions_ps(1:string db_name 2:string tbl_name 3:list part_vals, 4:i16 max_parts=-1) throws(1:MetaException o1, 2:NoSuchObjectException o2) list get_partitions_ps_with_auth(1:string db_name, 2:string tbl_name, 3:list part_vals, 4:i16 max_parts=-1, 5: string user_name, 6: list group_names) throws(1:NoSuchObjectException o1, 2:MetaException o2) list get_partition_names_ps(1:string db_name, 2:string tbl_name, 3:list part_vals, 4:i16 max_parts=-1) throws(1:MetaException o1, 2:NoSuchObjectException o2) list get_partitions_by_filter(1:string db_name 2:string tbl_name 3:string filter, 4:i16 max_parts=-1) throws(1:MetaException o1, 2:NoSuchObjectException o2) list get_partitions_by_names(1:string db_name 2:string tbl_name 3:list names) throws(1:MetaException o1, 2:NoSuchObjectException o2) bool drop_index_by_name(1:string db_name, 2:string tbl_name, 3:string index_name, 4:bool deleteData) throws(1:NoSuchObjectException o1, 2:MetaException o2) Index get_index_by_name(1:string db_name 2:string tbl_name, 3:string index_name) throws(1:MetaException o1, 2:NoSuchObjectException o2) list get_indexes(1:string db_name, 2:string tbl_name, 3:i16 max_indexes=-1) throws(1:NoSuchObjectException o1, 2:MetaException o2) list get_index_names(1:string db_name, 2:string tbl_name, 3:i16 max_indexes=-1) throws(1:MetaException o2) -- 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-2808) Add inputs/outputs for create table if not exists
Add inputs/outputs for create table if not exists - Key: HIVE-2808 URL: https://issues.apache.org/jira/browse/HIVE-2808 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Kevin Wilfong create table if not exists T(..) should have the following semantics: 1. If the table does not exist, T should be a output 2. If T already exists, T should be a input and output. -- 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-2837) insert into external tables should not be allowed
insert into external tables should not be allowed - Key: HIVE-2837 URL: https://issues.apache.org/jira/browse/HIVE-2837 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain This is a very risky thing to allow. Since, the external tables can point to any user location, which can potentially corrupt some other tables. -- 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-2838) cleanup readentity/writeentity
cleanup readentity/writeentity -- Key: HIVE-2838 URL: https://issues.apache.org/jira/browse/HIVE-2838 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain Ideally, there should be one common entity instead of readentity/writeentity. Unfortunately, that would be a backward incompatible change since users os hive might have written there own hooks, where they are using readentity/writeentity. We should atleast create a common class, and then we can deprecate read/write entity later, for a new release. For now, I propose to make a backward compatible change. -- 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-2844) Add Mysql concurrency manager
Add Mysql concurrency manager - Key: HIVE-2844 URL: https://issues.apache.org/jira/browse/HIVE-2844 Project: Hive Issue Type: New Feature Reporter: Namit Jain A pluggable concurrency model was added for hive https://issues.apache.org/jira/browse/HIVE-1293. It would be very useful to have a MYSQL based implementation for the above. The metadata load should not create a problem for mysql even for very large clusters. -- 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-2845) Add support for index joins in Hive
Add support for index joins in Hive --- Key: HIVE-2845 URL: https://issues.apache.org/jira/browse/HIVE-2845 Project: Hive Issue Type: New Feature Reporter: Namit Jain Hive supports indexes, which are used for filters currently. It would be very useful to add support for index-based joins in Hive. If 2 tables A and B are being joined, and an index exists on the join key of A, B can be scanned (by the mappers), and for each row in B, a lookup for the corresponding row in A can be performed. This can be very useful for some usecases. -- 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-2846) Enhance bucketing and sorting support in hive
Enhance bucketing and sorting support in hive - Key: HIVE-2846 URL: https://issues.apache.org/jira/browse/HIVE-2846 Project: Hive Issue Type: New Feature Reporter: Namit Jain This task consists of a couple of sub-tasks. 1. Removing the map-join hint completely. Moving all processing to runtime. Currently, bucketed map joins and sort merge joins are completely driven off hints. 2. Create a performance suite for performance for bucketed map-joins for different scenarios: the big table has many buckets, whereas the small table has fewer buckets etc. 3. Infer bucketing and sorting from the user query, and store that in the metastore. This can be used for follow-up queries on those outputs. -- 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-2847) Add support for query rewrite from the metadata
Add support for query rewrite from the metadata --- Key: HIVE-2847 URL: https://issues.apache.org/jira/browse/HIVE-2847 Project: Hive Issue Type: New Feature Reporter: Namit Jain A simple query like: select count(1) from T should be able to get the results from the metadata instead of scanning the complete input table T. 2. the metadata only queries today does not scale to a very large number of partitions - that needs to be fixed. -- 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-2892) Maintain number of files in the metastore as part of hive statistics collection
Maintain number of files in the metastore as part of hive statistics collection --- Key: HIVE-2892 URL: https://issues.apache.org/jira/browse/HIVE-2892 Project: Hive Issue Type: New Feature Reporter: Namit Jain This should not be any different than the size of each partition. The number of files will only be valid at the granularity of the partition. They need not be maintained at the table level. -- 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-2929) race condition in DAG execute tasks for hive
race condition in DAG execute tasks for hive Key: HIVE-2929 URL: https://issues.apache.org/jira/browse/HIVE-2929 Project: Hive Issue Type: Bug Reporter: Namit Jain select ... ( SubQuery involving MapReduce union all SubQuery involving MapReduce ); or select ... (SubQuery involving MapReduce) join (SubQuery involving MapReduce) ; If both the subQueries finish at nearly the same time, there is a race condition in which the results of the subQuery finishing last will be completely missed. -- 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-2931) conf settings may be ignored
conf settings may be ignored Key: HIVE-2931 URL: https://issues.apache.org/jira/browse/HIVE-2931 Project: Hive Issue Type: Bug Reporter: Namit Jain This is a pretty serious problem. If a conf variable is changed, Hive may not pick up the variable unless the metastore variables are changed. When any session variables are changed, it might be simpler to update the corresponding Hive conf. -- 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-2932) TestHBaseCliDriver breaking in trunk
TestHBaseCliDriver breaking in trunk Key: HIVE-2932 URL: https://issues.apache.org/jira/browse/HIVE-2932 Project: Hive Issue Type: Bug Reporter: Namit Jain I am getting 3 failures in clean trunk. -- 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-2513) create a test to verify that partition pruning works for partitioned views with a union
create a test to verify that partition pruning works for partitioned views with a union --- Key: HIVE-2513 URL: https://issues.apache.org/jira/browse/HIVE-2513 Project: Hive Issue Type: Test Reporter: Namit Jain Assignee: Namit Jain It would be good to have a test to check partition pruning on a view like: create view t1 partitioned on (ds) as select * from ( select key, value, ds from t1_new union all select key, value, t1_old.ds from t1_old join t1_mapping on t1_old.keymap = t1_mapping.keymap and t1_old.ds = t1_mapping.ds ) subq; While adding the test, I found that the lineage is broken for this. Will file a separate issue for that. -- 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-2514) lineage info wrong in some cases
lineage info wrong in some cases Key: HIVE-2514 URL: https://issues.apache.org/jira/browse/HIVE-2514 Project: Hive Issue Type: Bug Reporter: Namit Jain It can be isolated further, but for https://issues.apache.org/jira/browse/HIVE-2513, it is definitely broken. -- 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-2516) cleaunup QTestUtil: use test.data.files as current directory if one not specified
cleaunup QTestUtil: use test.data.files as current directory if one not specified - Key: HIVE-2516 URL: https://issues.apache.org/jira/browse/HIVE-2516 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.2516.1.patch This will help debugging via eclipse. -- 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-2533) test load_fs.q failing
test load_fs.q failing -- Key: HIVE-2533 URL: https://issues.apache.org/jira/browse/HIVE-2533 Project: Hive Issue Type: Bug Reporter: Namit Jain -- 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-2546) add explain formatted
add explain formatted - Key: HIVE-2546 URL: https://issues.apache.org/jira/browse/HIVE-2546 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain The output can be a json string. This can be easily parsed by some program that way. -- 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-2555) Make the hashmap in map-side group by pluggable
Make the hashmap in map-side group by pluggable --- Key: HIVE-2555 URL: https://issues.apache.org/jira/browse/HIVE-2555 Project: Hive Issue Type: New Feature Reporter: Namit Jain There are a couple of implementations available (other than java.util.HashMap) - COLT, TROVE etc. to name a few. If the hashmap was pluggable, it would be easy to play around with different hash maps and tune performance. -- 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-2566) reduce the number map-reduce jobs for union all
reduce the number map-reduce jobs for union all --- Key: HIVE-2566 URL: https://issues.apache.org/jira/browse/HIVE-2566 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain A query like: select s.key, s.value from ( select key, value from src2 where key < 10 union all select key, value from src3 where key < 10 union all select key, value from src4 where key < 10 union all select key, count(1) as value from src5 group by key )s; should run the last sub-query 'select key, count(1) as value from src5 group by key' as a map-reduce job. And then the union should be a map-only job reading from the first 3 map-only subqueries and the output of the last map-reduce job. The current plan is very inefficient. -- 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
