[jira] [Updated] (HIVE-2476) Update project description and wiki link in ivy.xml files
[
https://issues.apache.org/jira/browse/HIVE-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2476:
---
Attachment: hive-2476.patch
Patch to update */ivy.xml files as noted above.
> Update project description and wiki link in ivy.xml files
> -
>
> Key: HIVE-2476
> URL: https://issues.apache.org/jira/browse/HIVE-2476
> Project: Hive
> Issue Type: Sub-task
> Components: Documentation
>Reporter: John Sichi
> Attachments: hive-2476.patch
>
>
> Needs to be done for all subdirs; they currently have
> {noformat}
> Hive is a data warehouse infrastructure built on top of Hadoop see
> http://wiki.apache.org/hadoop/Hive
> {noformat}
> See HIVE-2435 for updated description.
--
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] [Resolved] (HIVE-1730) Keep the mapping between jdbm file name with bucket file name during the compile time
[ https://issues.apache.org/jira/browse/HIVE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1730. Resolution: Not A Problem With HIVE-1754 jdbm is removed so this is no longer relevant. > Keep the mapping between jdbm file name with bucket file name during the > compile time > - > > Key: HIVE-1730 > URL: https://issues.apache.org/jira/browse/HIVE-1730 > Project: Hive > Issue Type: Sub-task > Components: Query Processor >Affects Versions: 0.7.0 >Reporter: Liyin Tang >Assignee: Liyin Tang > > Right now, the new map join operator will figure out the jdbm file name > during the run time based some string function. > But we need to keep this mapping during the compile time, so the explain task > can understand which jdbm file the mapred task will need. -- 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] [Updated] (HIVE-1567) increase hive.mapjoin.maxsize to 10 million
[ https://issues.apache.org/jira/browse/HIVE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-1567: --- Attachment: hive-1567.patch I think with HIVE-1754 this configuration is no longer useful. Patch to remove it. > increase hive.mapjoin.maxsize to 10 million > --- > > Key: HIVE-1567 > URL: https://issues.apache.org/jira/browse/HIVE-1567 > Project: Hive > Issue Type: Improvement >Reporter: He Yongqiang > Attachments: hive-1567.patch > > > i saw in a very wide table, hive can process 1million rows in less than one > minute (select all columns). > setting the hive.mapjoin.maxsize to 100k is kind of too restrictive. Let's > increase this to 10 million. -- 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] [Updated] (HIVE-2476) Update project description and wiki link in ivy.xml files
[
https://issues.apache.org/jira/browse/HIVE-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2476:
---
Assignee: Ashutosh Chauhan
Status: Patch Available (was: Open)
> Update project description and wiki link in ivy.xml files
> -
>
> Key: HIVE-2476
> URL: https://issues.apache.org/jira/browse/HIVE-2476
> Project: Hive
> Issue Type: Sub-task
> Components: Documentation
>Reporter: John Sichi
>Assignee: Ashutosh Chauhan
> Attachments: hive-2476.patch
>
>
> Needs to be done for all subdirs; they currently have
> {noformat}
> Hive is a data warehouse infrastructure built on top of Hadoop see
> http://wiki.apache.org/hadoop/Hive
> {noformat}
> See HIVE-2435 for updated description.
--
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] [Updated] (HIVE-1567) increase hive.mapjoin.maxsize to 10 million
[ https://issues.apache.org/jira/browse/HIVE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-1567: --- Assignee: Ashutosh Chauhan Status: Patch Available (was: Open) > increase hive.mapjoin.maxsize to 10 million > --- > > Key: HIVE-1567 > URL: https://issues.apache.org/jira/browse/HIVE-1567 > Project: Hive > Issue Type: Improvement >Reporter: He Yongqiang >Assignee: Ashutosh Chauhan > Attachments: hive-1567.patch > > > i saw in a very wide table, hive can process 1million rows in less than one > minute (select all columns). > setting the hive.mapjoin.maxsize to 100k is kind of too restrictive. Let's > increase this to 10 million. -- 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] [Updated] (HIVE-1003) optimize metadata only queries
[ https://issues.apache.org/jira/browse/HIVE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-1003: - Status: Open (was: Patch Available) cleaning up the patch > optimize metadata only queries > -- > > Key: HIVE-1003 > URL: https://issues.apache.org/jira/browse/HIVE-1003 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Namit Jain >Assignee: Marcin Kurczych > Attachments: HIVE-1003.1.patch > > > Queries like: > select max(ds) from T > where ds is a partitioning column should be optimized. -- 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] [Commented] (HIVE-1237) select coalesce(null) from src dies
[ https://issues.apache.org/jira/browse/HIVE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130784#comment-13130784 ] Namit Jain commented on HIVE-1237: -- +1 > select coalesce(null) from src dies > --- > > Key: HIVE-1237 > URL: https://issues.apache.org/jira/browse/HIVE-1237 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain >Assignee: Ashutosh Chauhan > Attachments: hive-1237.patch > > > select coalesce(null) from src ; > FAILED: Unknown exception: null -- 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] [Commented] (HIVE-1003) optimize metadata only queries
[ https://issues.apache.org/jira/browse/HIVE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130785#comment-13130785 ] Marcin Kurczych commented on HIVE-1003: --- I have finished my internship at Facebook. If you want to contact me you can reach me at Marcin Kurczych . Thanks! > optimize metadata only queries > -- > > Key: HIVE-1003 > URL: https://issues.apache.org/jira/browse/HIVE-1003 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Namit Jain >Assignee: Marcin Kurczych > Attachments: HIVE-1003.1.patch > > > Queries like: > select max(ds) from T > where ds is a partitioning column should be optimized. -- 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] [Commented] (HIVE-2512) After HIVE-2145, Hive disallow any use of function in cluster-by clause
[ https://issues.apache.org/jira/browse/HIVE-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130788#comment-13130788 ] Ning Zhang commented on HIVE-2512: -- Cool. Thanks Chinna! Just a suggestions, I think reverting the change in HIVE-2145 and make a deeper investigation of why it threw NPE in the test case of HIVE-2145 and fix that seems to be a better solution. > After HIVE-2145, Hive disallow any use of function in cluster-by clause > --- > > Key: HIVE-2512 > URL: https://issues.apache.org/jira/browse/HIVE-2512 > Project: Hive > Issue Type: Bug >Reporter: Ning Zhang >Assignee: Chinna Rao Lalam > > After HIVE-2145, the following query returns a semantic analysis error: > FROM src SELECT * cluster by rand(); > FAILED: Error in semantic analysis: functions are not supported in order by > Looking back at HIVE-2145, it's clear that the patch is more restrictive than > necessary. > Chinna, are you able to work on it? Please let me know if you don't have > cycles to do it now. -- 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] [Commented] (HIVE-2505) Update junit jar in testlibs
[ https://issues.apache.org/jira/browse/HIVE-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130792#comment-13130792 ] He Yongqiang commented on HIVE-2505: looks good. running tests > Update junit jar in testlibs > > > Key: HIVE-2505 > URL: https://issues.apache.org/jira/browse/HIVE-2505 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2505.1.patch.txt > > -- 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] [Commented] (HIVE-2372) java.io.IOException: error=7, Argument list too long
[
https://issues.apache.org/jira/browse/HIVE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130793#comment-13130793
]
Sergey Tryuber commented on HIVE-2372:
--
Siying, what the limit we should set on this property? Limiting it to 132KB
won't work on kernels prior to 2.6.23, because there are other properties exist
and sum limit will exceed 132KB threshold for those kernels. May be we could
introduce on more property that (if set to true) will remove the key?
> java.io.IOException: error=7, Argument list too long
>
>
> Key: HIVE-2372
> URL: https://issues.apache.org/jira/browse/HIVE-2372
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: Sergey Tryuber
>Priority: Critical
>
> I execute a huge query on a table with a lot of 2-level partitions. There is
> a perl reducer in my query. Maps worked ok, but every reducer fails with the
> following exception:
> 2011-08-11 04:58:29,865 INFO org.apache.hadoop.hive.ql.exec.ScriptOperator:
> Executing [/usr/bin/perl, , ]
> 2011-08-11 04:58:29,866 INFO org.apache.hadoop.hive.ql.exec.ScriptOperator:
> tablename=null
> 2011-08-11 04:58:29,866 INFO org.apache.hadoop.hive.ql.exec.ScriptOperator:
> partname=null
> 2011-08-11 04:58:29,866 INFO org.apache.hadoop.hive.ql.exec.ScriptOperator:
> alias=null
> 2011-08-11 04:58:29,935 FATAL ExecReducer:
> org.apache.hadoop.hive.ql.metadata.HiveException: Hive Runtime Error while
> processing row (tag=0)
> {"key":{"reducesinkkey0":129390185139228,"reducesinkkey1":"8AF163CA6F"},"value":{"_col0":"8AF163CA6F","_col1":"2011-07-27
>
> 22:48:52","_col2":129390185139228,"_col3":2006,"_col4":4100,"_col5":"10017388=6","_col6":1063,"_col7":"NULL","_col8":"address.com","_col9":"NULL","_col10":"NULL"},"alias":0}
> at
> org.apache.hadoop.hive.ql.exec.ExecReducer.reduce(ExecReducer.java:256)
> at
> org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:468)
> at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:416)
> at org.apache.hadoop.mapred.Child$4.run(Child.java:268)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:396)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1115)
> at org.apache.hadoop.mapred.Child.main(Child.java:262)
> Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: Cannot
> initialize ScriptOperator
> at
> org.apache.hadoop.hive.ql.exec.ScriptOperator.processOp(ScriptOperator.java:320)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:84)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.ExtractOperator.processOp(ExtractOperator.java:45)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at
> org.apache.hadoop.hive.ql.exec.ExecReducer.reduce(ExecReducer.java:247)
> ... 7 more
> Caused by: java.io.IOException: Cannot run program "/usr/bin/perl":
> java.io.IOException: error=7, Argument list too long
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
> at
> org.apache.hadoop.hive.ql.exec.ScriptOperator.processOp(ScriptOperator.java:279)
> ... 15 more
> Caused by: java.io.IOException: java.io.IOException: error=7, Argument list
> too long
> at java.lang.UNIXProcess.(UNIXProcess.java:148)
> at java.lang.ProcessImpl.start(ProcessImpl.java:65)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
> ... 16 more
> It seems to me, I found the cause. ScriptOperator.java puts a lot of configs
> as environment variables to the child reduce process. One of variables is
> mapred.input.dir, which in my case more than 150KB. There are a huge amount
> of input directories in this variable. In short, the problem is that Linux
> (up to 2.6.23 kernel version) limits summary size of environment variables
> for child processes to 132KB. This problem could be solved by upgrading the
> kernel. But strings limitations still be 132KB per string in environment
> variable. So such huge variable doesn't work even on my home computer
> (2.6.32). You can read more information on
> (http://www.kernel.org/doc/man-pages/online/pages/man2/execve.2.html).
> For now all our work has been stopped because of this problem and I can't
> find the solution. The only solution, which seems to me more reasonable is to
> get ri
[jira] [Updated] (HIVE-2512) After HIVE-2145, Hive disallow any use of function in cluster-by clause
[ https://issues.apache.org/jira/browse/HIVE-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinna Rao Lalam updated HIVE-2512: --- Attachment: HIVE-2512.patch > After HIVE-2145, Hive disallow any use of function in cluster-by clause > --- > > Key: HIVE-2512 > URL: https://issues.apache.org/jira/browse/HIVE-2512 > Project: Hive > Issue Type: Bug >Reporter: Ning Zhang >Assignee: Chinna Rao Lalam > Attachments: HIVE-2512.patch > > > After HIVE-2145, the following query returns a semantic analysis error: > FROM src SELECT * cluster by rand(); > FAILED: Error in semantic analysis: functions are not supported in order by > Looking back at HIVE-2145, it's clear that the patch is more restrictive than > necessary. > Chinna, are you able to work on it? Please let me know if you don't have > cycles to do it now. -- 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] [Updated] (HIVE-2505) Update junit jar in testlibs
[ https://issues.apache.org/jira/browse/HIVE-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-2505: Attachment: junit-4.10.jar > Update junit jar in testlibs > > > Key: HIVE-2505 > URL: https://issues.apache.org/jira/browse/HIVE-2505 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2505.1.patch.txt, junit-4.10.jar > > -- 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] [Commented] (HIVE-2505) Update junit jar in testlibs
[ https://issues.apache.org/jira/browse/HIVE-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130862#comment-13130862 ] Kevin Wilfong commented on HIVE-2505: - After applying the patch junit-4.10.jar needs to be added to the directory trunk/testlibs/ The jar junit-3.8.1.jar needs to be removed from that same directory as well. > Update junit jar in testlibs > > > Key: HIVE-2505 > URL: https://issues.apache.org/jira/browse/HIVE-2505 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2505.1.patch.txt, junit-4.10.jar > > -- 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] [Commented] (HIVE-2512) After HIVE-2145, Hive disallow any use of function in cluster-by clause
[ https://issues.apache.org/jira/browse/HIVE-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130867#comment-13130867 ] Chinna Rao Lalam commented on HIVE-2512: SemanticAnalyzer.genReduceSinkPlan() added a function validation check for orderby and sortby in the same flow clusterby also executing so it is throwing execption for the clusterby also. Orderby and Sortby wont support the functions so need to add the function validation check. Now validation check is modified like it should check only for the orderby and sortby. Patch is uploaded and testcases are executing > After HIVE-2145, Hive disallow any use of function in cluster-by clause > --- > > Key: HIVE-2512 > URL: https://issues.apache.org/jira/browse/HIVE-2512 > Project: Hive > Issue Type: Bug >Reporter: Ning Zhang >Assignee: Chinna Rao Lalam > Attachments: HIVE-2512.patch > > > After HIVE-2145, the following query returns a semantic analysis error: > FROM src SELECT * cluster by rand(); > FAILED: Error in semantic analysis: functions are not supported in order by > Looking back at HIVE-2145, it's clear that the patch is more restrictive than > necessary. > Chinna, are you able to work on it? Please let me know if you don't have > cycles to do it now. -- 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] [Commented] (HIVE-2505) Update junit jar in testlibs
[ https://issues.apache.org/jira/browse/HIVE-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130869#comment-13130869 ] Ashutosh Chauhan commented on HIVE-2505: Instead of checking in the jar we should pull it from maven repos via ivy. Its available on http://repo1.maven.org/maven/ > Update junit jar in testlibs > > > Key: HIVE-2505 > URL: https://issues.apache.org/jira/browse/HIVE-2505 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2505.1.patch.txt, junit-4.10.jar > > -- 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] [Commented] (HIVE-2487) Bug from HIVE-2446, the code that calls client stats publishers run() methods is in wrong place, should be in the same method but inside of while (!rj.isComplete()) {} l
[
https://issues.apache.org/jira/browse/HIVE-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130873#comment-13130873
]
Ning Zhang commented on HIVE-2487:
--
Yongqiang, it seems you have committed this patch? Can you close this JIRA if
so?
> Bug from HIVE-2446, the code that calls client stats publishers run() methods
> is in wrong place, should be in the same method but inside of while
> (!rj.isComplete()) {} loop
>
>
> Key: HIVE-2487
> URL: https://issues.apache.org/jira/browse/HIVE-2487
> Project: Hive
> Issue Type: Bug
>Reporter: Robert Surówka
>Assignee: Robert Surówka
>Priority: Trivial
> Attachments: HIVE-2487.1.patch, HIVE-2487.1.patch, HIVE-2487.2.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] [Updated] (HIVE-2487) Bug from HIVE-2446, the code that calls client stats publishers run() methods is in wrong place, should be in the same method but inside of while (!rj.isComplete()) {} loo
[
https://issues.apache.org/jira/browse/HIVE-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
He Yongqiang updated HIVE-2487:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed, thanks Robert!
> Bug from HIVE-2446, the code that calls client stats publishers run() methods
> is in wrong place, should be in the same method but inside of while
> (!rj.isComplete()) {} loop
>
>
> Key: HIVE-2487
> URL: https://issues.apache.org/jira/browse/HIVE-2487
> Project: Hive
> Issue Type: Bug
>Reporter: Robert Surówka
>Assignee: Robert Surówka
>Priority: Trivial
> Attachments: HIVE-2487.1.patch, HIVE-2487.1.patch, HIVE-2487.2.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-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] [Updated] (HIVE-2513) create a test to verify that partition pruning works for partitioned views with a union
[ https://issues.apache.org/jira/browse/HIVE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2513: - Attachment: hive.2513.1.patch > 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 > Attachments: hive.2513.1.patch > > > 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] [Updated] (HIVE-2513) create a test to verify that partition pruning works for partitioned views with a union
[ https://issues.apache.org/jira/browse/HIVE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2513: - Status: Patch Available (was: Open) > 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 > Attachments: hive.2513.1.patch > > > 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-2515) Make Constant OIs work with UDTFs.
Make Constant OIs work with UDTFs. -- Key: HIVE-2515 URL: https://issues.apache.org/jira/browse/HIVE-2515 Project: Hive Issue Type: Improvement Reporter: Jonathan Chang Assignee: Jonathan Chang Priority: Minor UDTFs are the last shoe to drop for constant OIs. -- 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] [Updated] (HIVE-2500) Allow Hive to be debugged remotely
[ https://issues.apache.org/jira/browse/HIVE-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Surówka updated HIVE-2500: - Attachment: HIVE-2500.4.patch Reintroduced the change to the hive-env.sh.template that I missed in the last patch. Note: due to the change I was requested to make, to add debug options to HADOOP_CLIENT_OPTS instead of HADOOP_OPTS, the debugging won't work unless at some point HADOOP_CLIENT_OPTS will be introduced into HADOOP_OPTS (or will be passed to JVM directly). This could be possibly best done by adding line like: export HADOOP_OPTS="$HADOOP_OPTS $HADOOP_CLIENT_OPTS" to hadoop-env.sh > Allow Hive to be debugged remotely > -- > > Key: HIVE-2500 > URL: https://issues.apache.org/jira/browse/HIVE-2500 > Project: Hive > Issue Type: New Feature >Reporter: Robert Surówka >Assignee: Robert Surówka >Priority: Minor > Attachments: HIVE-2500.1.patch, HIVE-2500.2.patch, HIVE-2500.3.patch, > HIVE-2500.4.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] [Commented] (HIVE-2505) Update junit jar in testlibs
[ https://issues.apache.org/jira/browse/HIVE-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131140#comment-13131140 ] John Sichi commented on HIVE-2505: -- +1 on what Ashutosh said; when upgrading something which is currently checked into lib but available in a maven repo, we should svn rm the old jar and add an ivy download to the build. > Update junit jar in testlibs > > > Key: HIVE-2505 > URL: https://issues.apache.org/jira/browse/HIVE-2505 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2505.1.patch.txt, junit-4.10.jar > > -- 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] [Commented] (HIVE-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131156#comment-13131156 ] John Sichi commented on HIVE-2509: -- Just checking...is there a case where the bigint type is actually important? HIVE-872 was supposed to address the implicit conversion cases. > Literal bigint > -- > > Key: HIVE-2509 > URL: https://issues.apache.org/jira/browse/HIVE-2509 > Project: Hive > Issue Type: New Feature >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Attachments: D15.1.patch, D15.1.patch > > > Typing bigints is a pain because you have to write CAST(0 AS BIGINT). We > should let people type 0L instead. -- 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] [Updated] (HIVE-2516) cleaunup QTestUtil: use test.data.files as current directory if one not specified
[ https://issues.apache.org/jira/browse/HIVE-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2516: - Attachment: hive.2516.1.patch > 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] [Updated] (HIVE-2516) cleaunup QTestUtil: use test.data.files as current directory if one not specified
[ https://issues.apache.org/jira/browse/HIVE-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2516: - Status: Patch Available (was: Open) > 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] [Commented] (HIVE-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131169#comment-13131169 ] Jonathan Chang commented on HIVE-2509: -- There are two issues: 1.) There are actually lots of UDFs which are pretty sensitive to type. In particular, widening will not handle cases where array needs to be widened to array (there's a reason this sort of thing isn't autocasted in C++, Java, etc.). 2.) I generally think widening is a bad idea because it makes people less careful with types. For example, without looking, what will > explain select * from (select '0' from akramer_one_row union all select > 12345678900 from akramer_one_row) a; return as the type of the outer query? The answer is pretty terrible; if any other language did this to you you'd be pretty furious. > Literal bigint > -- > > Key: HIVE-2509 > URL: https://issues.apache.org/jira/browse/HIVE-2509 > Project: Hive > Issue Type: New Feature >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Attachments: D15.1.patch, D15.1.patch > > > Typing bigints is a pain because you have to write CAST(0 AS BIGINT). We > should let people type 0L instead. -- 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] [Commented] (HIVE-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131186#comment-13131186 ] John Sichi commented on HIVE-2509: -- 1) So for the array case, you're going to stick an L on the end of every literal in the array? An explicit CAST seems cleaner in that case (assuming it works). What are some other cases? I'd like to understand them better before we add more Hive-specific syntax (I'm not aware of any other SQL parsers that use the L suffix). 2) In standard SQL, that would be an error since strings and numbers are not union-compatible. Simple. I wish Hive followed standard SQL in this and many other areas (such as comparison strictness). > Literal bigint > -- > > Key: HIVE-2509 > URL: https://issues.apache.org/jira/browse/HIVE-2509 > Project: Hive > Issue Type: New Feature >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Attachments: D15.1.patch, D15.1.patch > > > Typing bigints is a pain because you have to write CAST(0 AS BIGINT). We > should let people type 0L instead. -- 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] [Commented] (HIVE-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131201#comment-13131201 ] Jonathan Chang commented on HIVE-2509: -- 1.) You can't cast array to array in Hive which is why we had to write an FB UDF for this exact problem. Right now you need to pass in an instance of the desired type which is annoying with BIGINTs. This starts to become a deep rabbit hole. For example, how do you tell if an array is equal to [0L]? Turns out you can't compare arrays in Hive. So we have a UDF, which chokes if you try to compare array to array, which is IMO reasonable behavior because the complexity/corner cases which we've been talking about here (and on point #2) just gets moved into this UDF which is untenable for the large library of UDFs we have. 2.) Yes, I agree that an error would be good in those cases. Can we make that happen? (Unrelated issue but type widening still fails with NULLs; in general I think type widening is uber complicated and prone to all sorts of issues we wouldn't have if we were more type safe throughout.) > Literal bigint > -- > > Key: HIVE-2509 > URL: https://issues.apache.org/jira/browse/HIVE-2509 > Project: Hive > Issue Type: New Feature >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Attachments: D15.1.patch, D15.1.patch > > > Typing bigints is a pain because you have to write CAST(0 AS BIGINT). We > should let people type 0L instead. -- 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] [Commented] (HIVE-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131209#comment-13131209 ] Jonathan Chang commented on HIVE-2509: -- To put it another way, once you have complex types (arrays, maps, struct and the like) you either need strong typing (a la C++, Java, etc.) or full-on duck typing (a la Python). I don't think any language has successfully maintained a middle ground (what Hive is trying to do right now). > Literal bigint > -- > > Key: HIVE-2509 > URL: https://issues.apache.org/jira/browse/HIVE-2509 > Project: Hive > Issue Type: New Feature >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Attachments: D15.1.patch, D15.1.patch > > > Typing bigints is a pain because you have to write CAST(0 AS BIGINT). We > should let people type 0L instead. -- 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] [Commented] (HIVE-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131216#comment-13131216 ] Jonathan Chang commented on HIVE-2509: -- This also matters in a few other places like CTAS. In any case, this is a pretty low-risk change and not too onerous on the code base so I hope this gets in... > Literal bigint > -- > > Key: HIVE-2509 > URL: https://issues.apache.org/jira/browse/HIVE-2509 > Project: Hive > Issue Type: New Feature >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Attachments: D15.1.patch, D15.1.patch > > > Typing bigints is a pain because you have to write CAST(0 AS BIGINT). We > should let people type 0L instead. -- 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] [Updated] (HIVE-2510) Hive throws Null Pointer Exception upon CREATE TABLE . .... if the given doesn't exist
[ https://issues.apache.org/jira/browse/HIVE-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Surówka updated HIVE-2510: - Attachment: HIVE-2510.2.patch New diff request at https://reviews.apache.org/r/2426/diff/2/ Changed fix to be more general and added tests. There is still an issue that: create table . (a string); doesn't work. But that's a topic for another Jira. > Hive throws Null Pointer Exception upon CREATE TABLE . > if the given doesn't exist > - > > Key: HIVE-2510 > URL: https://issues.apache.org/jira/browse/HIVE-2510 > Project: Hive > Issue Type: Bug >Reporter: Robert Surówka >Assignee: Robert Surówka >Priority: Trivial > Attachments: HIVE-2510.1.patch, HIVE-2510.2.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] [Commented] (HIVE-2486) Phabricator for code review
[ https://issues.apache.org/jira/browse/HIVE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131278#comment-13131278 ] jsichi (John Sichi) commented on HIVE-2486: --- ping > Phabricator for code review > --- > > Key: HIVE-2486 > URL: https://issues.apache.org/jira/browse/HIVE-2486 > Project: Hive > Issue Type: Bug >Reporter: Marek Sapota > Attachments: D9.1.diff, D9.2.diff, SOAP, SOAP, TEST, x > > > Replacing Review Board with Phabricator and Differential. -- 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] [Commented] (HIVE-2486) Phabricator for code review
[ https://issues.apache.org/jira/browse/HIVE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131281#comment-13131281 ] Phabricator commented on HIVE-2486: --- ping > Phabricator for code review > --- > > Key: HIVE-2486 > URL: https://issues.apache.org/jira/browse/HIVE-2486 > Project: Hive > Issue Type: Bug >Reporter: Marek Sapota > Attachments: D9.1.diff, D9.2.diff, SOAP, SOAP, TEST, x > > > Replacing Review Board with Phabricator and Differential. -- 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] [Updated] (HIVE-2515) Make Constant OIs work with UDTFs.
[ https://issues.apache.org/jira/browse/HIVE-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2515: -- Attachment: D33.1.patch jonchang requested code review of "[jira] [HIVE-2515] Make Constant OIs work with UDTFs.". Reviewers: DUMMY_REVIEWER HIVE-2515 UDTFs are the last shoe to drop for constant OIs. TEST PLAN EMPTY REVISION DETAIL http://reviews.facebook.net/D33 AFFECTED FILES ql/src/java/org/apache/hadoop/hive/ql/exec/ColumnInfo.java ql/src/java/org/apache/hadoop/hive/ql/exec/FunctionRegistry.java ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDTFStack.java ql/src/test/queries/clientpositive/udtf_stack.q ql/src/test/results/clientpositive/show_functions.q.out ql/src/test/results/clientpositive/udtf_stack.q.out MANAGE HERALD DIFFERENTIAL RULES http://reviews.facebook.net/herald/view/differential/ WHY DID I GET THIS EMAIL? http://reviews.facebook.net/herald/transcript/69/ Tip: use the X-Herald-Rules header to filter Herald messages in your client. > Make Constant OIs work with UDTFs. > -- > > Key: HIVE-2515 > URL: https://issues.apache.org/jira/browse/HIVE-2515 > Project: Hive > Issue Type: Improvement >Reporter: Jonathan Chang >Assignee: Jonathan Chang >Priority: Minor > Attachments: D33.1.patch, D33.1.patch > > > UDTFs are the last shoe to drop for constant OIs. -- 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] [Updated] (HIVE-2515) Make Constant OIs work with UDTFs.
[ https://issues.apache.org/jira/browse/HIVE-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2515: -- Attachment: D33.1.patch jonchang requested code review of "[jira] [HIVE-2515] Make Constant OIs work with UDTFs.". Reviewers: DUMMY_REVIEWER HIVE-2515 UDTFs are the last shoe to drop for constant OIs. TEST PLAN EMPTY REVISION DETAIL http://reviews.facebook.net/D33 AFFECTED FILES ql/src/java/org/apache/hadoop/hive/ql/exec/ColumnInfo.java ql/src/java/org/apache/hadoop/hive/ql/exec/FunctionRegistry.java ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDTFStack.java ql/src/test/queries/clientpositive/udtf_stack.q ql/src/test/results/clientpositive/show_functions.q.out ql/src/test/results/clientpositive/udtf_stack.q.out MANAGE HERALD DIFFERENTIAL RULES http://reviews.facebook.net/herald/view/differential/ WHY DID I GET THIS EMAIL? http://reviews.facebook.net/herald/transcript/69/ Tip: use the X-Herald-Rules header to filter Herald messages in your client. > Make Constant OIs work with UDTFs. > -- > > Key: HIVE-2515 > URL: https://issues.apache.org/jira/browse/HIVE-2515 > Project: Hive > Issue Type: Improvement >Reporter: Jonathan Chang >Assignee: Jonathan Chang >Priority: Minor > Attachments: D33.1.patch, D33.1.patch > > > UDTFs are the last shoe to drop for constant OIs. -- 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] [Commented] (HIVE-2486) Phabricator for code review
[ https://issues.apache.org/jira/browse/HIVE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131295#comment-13131295 ] Phabricator commented on HIVE-2486: --- mareksapotafb has commented on the revision "[jira] [HIVE-2486] Phabricator for code review". How many emails will go to JIRA? REVISION DETAIL http://reviews.facebook.net/D9 > Phabricator for code review > --- > > Key: HIVE-2486 > URL: https://issues.apache.org/jira/browse/HIVE-2486 > Project: Hive > Issue Type: Bug >Reporter: Marek Sapota > Attachments: D9.1.diff, D9.2.diff, SOAP, SOAP, TEST, x > > > Replacing Review Board with Phabricator and Differential. -- 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] [Commented] (HIVE-2486) Phabricator for code review
[ https://issues.apache.org/jira/browse/HIVE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131294#comment-13131294 ] Phabricator commented on HIVE-2486: --- mareksapotafb has commented on the revision "[jira] [HIVE-2486] Phabricator for code review". How many emails will go to JIRA? REVISION DETAIL http://reviews.facebook.net/D9 > Phabricator for code review > --- > > Key: HIVE-2486 > URL: https://issues.apache.org/jira/browse/HIVE-2486 > Project: Hive > Issue Type: Bug >Reporter: Marek Sapota > Attachments: D9.1.diff, D9.2.diff, SOAP, SOAP, TEST, x > > > Replacing Review Board with Phabricator and Differential. -- 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] [Assigned] (HIVE-2517) Support group by on union and struct type
[ https://issues.apache.org/jira/browse/HIVE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan reassigned HIVE-2517: -- Assignee: Ashutosh Chauhan > Support group by on union and struct type > - > > Key: HIVE-2517 > URL: https://issues.apache.org/jira/browse/HIVE-2517 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: hive-2517.patch > > > Currently group by on struct and union types are not supported. This issue > will enable support for those. -- 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] [Updated] (HIVE-2517) Support group by on union and struct type
[ https://issues.apache.org/jira/browse/HIVE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2517: --- Attachment: hive-2517.patch Patch which enables this support. Test cases included. > Support group by on union and struct type > - > > Key: HIVE-2517 > URL: https://issues.apache.org/jira/browse/HIVE-2517 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: hive-2517.patch > > > Currently group by on struct and union types are not supported. This issue > will enable support for those. -- 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] [Updated] (HIVE-2517) Support group by on union and struct type
[ https://issues.apache.org/jira/browse/HIVE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2517: --- Status: Patch Available (was: Open) > Support group by on union and struct type > - > > Key: HIVE-2517 > URL: https://issues.apache.org/jira/browse/HIVE-2517 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: hive-2517.patch > > > Currently group by on struct and union types are not supported. This issue > will enable support for those. -- 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-2517) Support group by on union and struct type
Support group by on union and struct type - Key: HIVE-2517 URL: https://issues.apache.org/jira/browse/HIVE-2517 Project: Hive Issue Type: New Feature Components: Query Processor Reporter: Ashutosh Chauhan Attachments: hive-2517.patch Currently group by on struct and union types are not supported. This issue will enable support for those. -- 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
Review Request: Support for grouping on union and struct type.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2459/ --- Review request for hive, John Sichi, Yongqiang He, Ning Zhang, and namit jain. Summary --- Support for grouping on union and struct type. This addresses bug HIVE-2517. https://issues.apache.org/jira/browse/HIVE-2517 Diffs - trunk/ql/src/test/queries/clientpositive/groupby_complex_types.q 1186610 trunk/ql/src/test/results/clientpositive/groupby_complex_types.q.out 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryFactory.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinarySerDe.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryUnion.java PRE-CREATION trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryUtils.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/objectinspector/LazyBinaryObjectInspectorFactory.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/objectinspector/LazyBinaryUnionObjectInspector.java PRE-CREATION trunk/serde/src/java/org/apache/hadoop/hive/serde2/objectinspector/ObjectInspectorUtils.java 1186610 Diff: https://reviews.apache.org/r/2459/diff Testing --- Added *.q tests Thanks, Ashutosh
[jira] [Commented] (HIVE-2517) Support group by on union and struct type
[ https://issues.apache.org/jira/browse/HIVE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131368#comment-13131368 ] jirapos...@reviews.apache.org commented on HIVE-2517: - --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2459/ --- Review request for hive, John Sichi, Yongqiang He, Ning Zhang, and namit jain. Summary --- Support for grouping on union and struct type. This addresses bug HIVE-2517. https://issues.apache.org/jira/browse/HIVE-2517 Diffs - trunk/ql/src/test/queries/clientpositive/groupby_complex_types.q 1186610 trunk/ql/src/test/results/clientpositive/groupby_complex_types.q.out 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryFactory.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinarySerDe.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryUnion.java PRE-CREATION trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryUtils.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/objectinspector/LazyBinaryObjectInspectorFactory.java 1186610 trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/objectinspector/LazyBinaryUnionObjectInspector.java PRE-CREATION trunk/serde/src/java/org/apache/hadoop/hive/serde2/objectinspector/ObjectInspectorUtils.java 1186610 Diff: https://reviews.apache.org/r/2459/diff Testing --- Added *.q tests Thanks, Ashutosh > Support group by on union and struct type > - > > Key: HIVE-2517 > URL: https://issues.apache.org/jira/browse/HIVE-2517 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: hive-2517.patch > > > Currently group by on struct and union types are not supported. This issue > will enable support for those. -- 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] [Resolved] (HIVE-1243) CombineHiveInputFormat breaks.
[ https://issues.apache.org/jira/browse/HIVE-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1243. Resolution: Cannot Reproduce Closing as no longer reproducible on trunk. > CombineHiveInputFormat breaks. > -- > > Key: HIVE-1243 > URL: https://issues.apache.org/jira/browse/HIVE-1243 > Project: Hive > Issue Type: Bug >Affects Versions: 0.6.0 >Reporter: He Yongqiang > > set hive.input.format = > org.apache.hadoop.hive.ql.io.CombineHiveInputFormat;set > mapred.min.split.size.per.node=8;set hive.exec.compress.output = true;set > mapred.min.split.size=256; > drop table combine1_1;create table combine1_1(key string, value string) > stored as textfile; > insert overwrite table combine1_1 select * from src; -- 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] [Resolved] (HIVE-830) disable hive.optimize.ppd
[ https://issues.apache.org/jira/browse/HIVE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-830. --- Resolution: Not A Problem In trunk, it is on by default. Closing the ticket. > disable hive.optimize.ppd > - > > Key: HIVE-830 > URL: https://issues.apache.org/jira/browse/HIVE-830 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain > > Predicate pushdown has been running for some time, and seems reasonably > stable. > The new partition pruner depends on that - we should not let the use disale > it. -- 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
