[jira] [Updated] (HIVE-2099) GROUP BY rules not applied correctly for select *
[ https://issues.apache.org/jira/browse/HIVE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2099: - Status: Open (was: Patch Available) GROUP BY rules not applied correctly for select * - Key: HIVE-2099 URL: https://issues.apache.org/jira/browse/HIVE-2099 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.7.0, 0.6.0, 0.8.0, 0.9.0 Reporter: John Sichi Assignee: Chinna Rao Lalam Attachments: HIVE-2099.1.patch, HIVE-2099.patch This fails as expected: select foo, bar from pokes group by foo; This succeeds, which is incorrect: select * from pokes group by foo; I verified this as far back as 0.6, so maybe it has always been this 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] [Commented] (HIVE-2613) HiveCli eclipse launch configuration hangs
[ https://issues.apache.org/jira/browse/HIVE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13159555#comment-13159555 ] John Sichi commented on HIVE-2613: -- +1, will commit when tests pass. HiveCli eclipse launch configuration hangs -- Key: HIVE-2613 URL: https://issues.apache.org/jira/browse/HIVE-2613 Project: Hive Issue Type: Bug Components: Build Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-2613.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-2362) HiveConf properties not appearing in the output of 'set' or 'set -v'
[ https://issues.apache.org/jira/browse/HIVE-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13159625#comment-13159625 ] John Sichi commented on HIVE-2362: -- Need a testcase, right? HiveConf properties not appearing in the output of 'set' or 'set -v' Key: HIVE-2362 URL: https://issues.apache.org/jira/browse/HIVE-2362 Project: Hive Issue Type: Bug Components: CLI, Configuration Reporter: Carl Steinbach Assignee: Jakob Homan Priority: Blocker Fix For: 0.8.0 Attachments: HIVE-2362.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] [Updated] (HIVE-2613) HiveCli eclipse launch configuration hangs
[ https://issues.apache.org/jira/browse/HIVE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2613: - Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to trunk. Thanks Carl! HiveCli eclipse launch configuration hangs -- Key: HIVE-2613 URL: https://issues.apache.org/jira/browse/HIVE-2613 Project: Hive Issue Type: Bug Components: Build Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach Fix For: 0.9.0 Attachments: HIVE-2613.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
Re: Review Request: GROUP BY rules not applied correctly for select *
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2922/#review3550 --- trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java https://reviews.apache.org/r/2922/#comment7911 Rather than adding special-case code to handle this, wouldn't it be better to make genColListRegex call genExprNodeDesc (which is what normally detects the error)? This would avoid extra code, and would also make this apply to the other regex cases. - John On 2011-11-23 14:06:54, chinna wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2922/ --- (Updated 2011-11-23 14:06:54) Review request for hive and John Sichi. Summary --- Select * case provided group by validation like select columns list is subset or equal to the group by columns list. If it violates this validation will throw exception. This addresses bug HIVE-2099. https://issues.apache.org/jira/browse/HIVE-2099 Diffs - trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 1203044 trunk/ql/src/test/queries/clientnegative/groupby_select_all.q PRE-CREATION trunk/ql/src/test/queries/clientnegative/groupby_select_all_alias.q PRE-CREATION trunk/ql/src/test/queries/clientnegative/groupby_select_all_join.q PRE-CREATION trunk/ql/src/test/queries/clientnegative/groupby_select_all_subquery.q PRE-CREATION trunk/ql/src/test/queries/clientnegative/groupby_select_all_subquery_unionall.q PRE-CREATION trunk/ql/src/test/queries/clientpositive/groupby_select_all.q PRE-CREATION trunk/ql/src/test/results/clientnegative/groupby_select_all.q.out PRE-CREATION trunk/ql/src/test/results/clientnegative/groupby_select_all_alias.q.out PRE-CREATION trunk/ql/src/test/results/clientnegative/groupby_select_all_join.q.out PRE-CREATION trunk/ql/src/test/results/clientnegative/groupby_select_all_subquery.q.out PRE-CREATION trunk/ql/src/test/results/clientnegative/groupby_select_all_subquery_unionall.q.out PRE-CREATION trunk/ql/src/test/results/clientpositive/groupby_select_all.q.out PRE-CREATION Diff: https://reviews.apache.org/r/2922/diff Testing --- All unit tests passed and added new testcases Thanks, chinna
Re: please, check bug and a bunch of udf
On Nov 21, 2011, at 8:17 PM, 준호 조 wrote: hive-2332, hive-2329 and hive-2253 are all bug of hive. also, it is critical in our case and we only modified a few lines Per Carl's comments in JIRA, please mark these as patch available if you think they're ready for review by a committer. In addition, we contributed to many udfs which provide oracle functions. (hive-2361) I have HIVE-2523 (builtins support) ready for commit, so once we get the 0.8 release out, we can look into that. JVS
[jira] [Updated] (HIVE-1626) stop using java.util.Stack
[ https://issues.apache.org/jira/browse/HIVE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-1626: - Comment: was deleted (was: Testing, please ignore.) stop using java.util.Stack -- Key: HIVE-1626 URL: https://issues.apache.org/jira/browse/HIVE-1626 Project: Hive Issue Type: Improvement Components: Query Processor Affects Versions: 0.7.0 Reporter: John Sichi Assignee: John Sichi We currently use Stack as part of the generic node walking library. Stack should not be used for this since its inheritance from Vector incurs superfluous synchronization overhead. Most projects end up adding an ArrayStack implementation and using that 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-1626) stop using java.util.Stack
[ https://issues.apache.org/jira/browse/HIVE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-1626: - Comment: was deleted (was: More testing. ) stop using java.util.Stack -- Key: HIVE-1626 URL: https://issues.apache.org/jira/browse/HIVE-1626 Project: Hive Issue Type: Improvement Components: Query Processor Affects Versions: 0.7.0 Reporter: John Sichi Assignee: John Sichi We currently use Stack as part of the generic node walking library. Stack should not be used for this since its inheritance from Vector incurs superfluous synchronization overhead. Most projects end up adding an ArrayStack implementation and using that 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-1626) stop using java.util.Stack
[ https://issues.apache.org/jira/browse/HIVE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155610#comment-13155610 ] John Sichi commented on HIVE-1626: -- We can use ArrayDeque. http://docs.oracle.com/javase/6/docs/api/java/util/Deque.html stop using java.util.Stack -- Key: HIVE-1626 URL: https://issues.apache.org/jira/browse/HIVE-1626 Project: Hive Issue Type: Improvement Components: Query Processor Affects Versions: 0.7.0 Reporter: John Sichi Assignee: John Sichi We currently use Stack as part of the generic node walking library. Stack should not be used for this since its inheritance from Vector incurs superfluous synchronization overhead. Most projects end up adding an ArrayStack implementation and using that 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] [Resolved] (HIVE-2593) avoid referencing /tmp in tests
[ https://issues.apache.org/jira/browse/HIVE-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2593. -- Resolution: Fixed Fix Version/s: 0.9.0 Release Note: Hive CLI variable expansion now applies to shell commands as well. Hadoop Flags: Reviewed Committed to trunk. Thanks Marek! Can you grant ASF rights on latest patch? avoid referencing /tmp in tests --- Key: HIVE-2593 URL: https://issues.apache.org/jira/browse/HIVE-2593 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Reporter: John Sichi Assignee: Marek Sapota Fix For: 0.9.0 Attachments: HIVE-2593.D501.1.patch, HIVE-2593.D501.2.patch, HIVE-2593.D501.3.patch, HIVE-2593.D501.4.patch, HIVE-2593.D501.5.patch, HIVE-2593.D501.6.patch, HIVE-2593.D501.7.patch, HIVE-2593.D501.8.patch This is what is causing parallel tests to fail when multiple instances run on the same node. I grepped for /tmp in ql/src/test/queries/clientpositive and the results match the test failures I'm getting. -- 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-2592) ConstantOI doesn't always propagate to UDAF
[ https://issues.apache.org/jira/browse/HIVE-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154436#comment-13154436 ] John Sichi commented on HIVE-2592: -- Sure. ConstantOI doesn't always propagate to UDAF --- Key: HIVE-2592 URL: https://issues.apache.org/jira/browse/HIVE-2592 Project: Hive Issue Type: Bug Reporter: Jonathan Chang Assignee: Jonathan Chang Depending on the query plan, a UDAF may not actually get a constant OI. E.g., set hive.map.aggr=false; SELECT percentile_approx(cast(substr(src.value,5) AS double), 0.5) 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
Re: [VOTE] Apache Hive 0.8.0 Release Candidate 1
On Nov 18, 2011, at 5:19 PM, Carl Steinbach wrote: Apache Hive 0.8.0 Release Candidate 1 is available here: http://people.apache.org/~cws/hive-0.8.0-candidate-1/ Please test and vote. Thanks Carl, I'm running through ant test on the source tarball now. Are you going to be able to take care of HIVE-2436 and HIVE-2437 as part of updating the website for the 0.8.0 release? JVS
[jira] [Commented] (HIVE-2561) Add an annotation to UDFs to allow them to specify additional FILE/JAR resources necessary for execution
[ https://issues.apache.org/jira/browse/HIVE-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154525#comment-13154525 ] John Sichi commented on HIVE-2561: -- @Jon: This JIRA issue should be renamed since you went with the method override approach instead of annotation. Add an annotation to UDFs to allow them to specify additional FILE/JAR resources necessary for execution Key: HIVE-2561 URL: https://issues.apache.org/jira/browse/HIVE-2561 Project: Hive Issue Type: New Feature Reporter: Jonathan Chang Assignee: Jonathan Chang Attachments: HIVE-2561.D507.1.patch Often times UDFs will have dependencies to external JARs/FILEs. It makes sense for these to be encoded by the UDF (rather than having the caller remember the set of files that need to be ADDed). Let's add an annotation to UDFs which will cause these resources to be auto-added. -- 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-2593) avoid referencing /tmp in tests
[ https://issues.apache.org/jira/browse/HIVE-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154537#comment-13154537 ] John Sichi commented on HIVE-2593: -- OK I'll wait for an update which fixes hook_context_cs. avoid referencing /tmp in tests --- Key: HIVE-2593 URL: https://issues.apache.org/jira/browse/HIVE-2593 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Reporter: John Sichi Assignee: Marek Sapota Attachments: HIVE-2593.D501.1.patch, HIVE-2593.D501.2.patch, HIVE-2593.D501.3.patch This is what is causing parallel tests to fail when multiple instances run on the same node. I grepped for /tmp in ql/src/test/queries/clientpositive and the results match the test failures I'm getting. -- 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-2569) Too much debugging info on console if a job failed
[ https://issues.apache.org/jira/browse/HIVE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2569. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Committed to trunk, thanks Ning! Too much debugging info on console if a job failed -- Key: HIVE-2569 URL: https://issues.apache.org/jira/browse/HIVE-2569 Project: Hive Issue Type: Improvement Reporter: Ning Zhang Assignee: Ning Zhang Priority: Minor Fix For: 0.9.0 Attachments: D375.1.patch When a job failed and Hive client tries to get the error message from failed task, it printed the following info on console for each task: Examining task ID: task_201110112120_773499_m_37 from job job_201110112120_773499 This should be shorten significantly. -- 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-2569) Too much debugging info on console if a job failed
[ https://issues.apache.org/jira/browse/HIVE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2569: - Component/s: Diagnosability Too much debugging info on console if a job failed -- Key: HIVE-2569 URL: https://issues.apache.org/jira/browse/HIVE-2569 Project: Hive Issue Type: Improvement Components: Diagnosability Reporter: Ning Zhang Assignee: Ning Zhang Priority: Minor Fix For: 0.9.0 Attachments: D375.1.patch When a job failed and Hive client tries to get the error message from failed task, it printed the following info on console for each task: Examining task ID: task_201110112120_773499_m_37 from job job_201110112120_773499 This should be shorten significantly. -- 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-2552) Omit incomplete Postgres upgrade scripts from release tarball
[ https://issues.apache.org/jira/browse/HIVE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2552: - Summary: Omit incomplete Postgres upgrade scripts from release tarball (was: Omit incomplete Postrgres upgrade scripts from release tarball) Omit incomplete Postgres upgrade scripts from release tarball - Key: HIVE-2552 URL: https://issues.apache.org/jira/browse/HIVE-2552 Project: Hive Issue Type: Task Components: Build Infrastructure, Metastore Reporter: Carl Steinbach Assignee: Carl Steinbach Fix For: 0.8.0 Attachments: HIVE-2552.1.patch.txt The Postgres metastore upgrade scripts are not officially supported, and at this point are incomplete. We should not include them in the release artifacts. -- 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-2552) Omit incomplete Postgres upgrade scripts from release tarball
[ https://issues.apache.org/jira/browse/HIVE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2552: - Resolution: Fixed Release Note: For the Hive 0.8 release, metastore persistence in Postgres is not officially supported. Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to trunk and 0.8. Thanks Carl! Omit incomplete Postgres upgrade scripts from release tarball - Key: HIVE-2552 URL: https://issues.apache.org/jira/browse/HIVE-2552 Project: Hive Issue Type: Task Components: Build Infrastructure, Metastore Reporter: Carl Steinbach Assignee: Carl Steinbach Fix For: 0.8.0 Attachments: HIVE-2552.1.patch.txt The Postgres metastore upgrade scripts are not officially supported, and at this point are incomplete. We should not include them in the release artifacts. -- 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-2552) Omit incomplete Postgres upgrade scripts from release tarball
[ https://issues.apache.org/jira/browse/HIVE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153134#comment-13153134 ] John Sichi commented on HIVE-2552: -- Added the release note to this issue. Omit incomplete Postgres upgrade scripts from release tarball - Key: HIVE-2552 URL: https://issues.apache.org/jira/browse/HIVE-2552 Project: Hive Issue Type: Task Components: Build Infrastructure, Metastore Reporter: Carl Steinbach Assignee: Carl Steinbach Fix For: 0.8.0 Attachments: HIVE-2552.1.patch.txt The Postgres metastore upgrade scripts are not officially supported, and at this point are incomplete. We should not include them in the release artifacts. -- 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-2598) Update README.txt file to use description from wiki
[ https://issues.apache.org/jira/browse/HIVE-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2598: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to 0.8 and trunk. Thanks Carl! Update README.txt file to use description from wiki --- Key: HIVE-2598 URL: https://issues.apache.org/jira/browse/HIVE-2598 Project: Hive Issue Type: Bug Components: Build Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach Fix For: 0.8.0 Attachments: HIVE-2598.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-2590) HBase bulk load wiki page improvements
[ https://issues.apache.org/jira/browse/HIVE-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152294#comment-13152294 ] John Sichi commented on HIVE-2590: -- If you want to update the wiki, create an account there, let me know the account name, and I'll grant you write access. HBase bulk load wiki page improvements -- Key: HIVE-2590 URL: https://issues.apache.org/jira/browse/HIVE-2590 Project: Hive Issue Type: Bug Components: Documentation, HBase Handler Reporter: Ben West Priority: Minor Labels: wiki Some suggestions on the page https://cwiki.apache.org/confluence/display/Hive/HBaseBulkLoad which seems kind of out of date: 1. It seems like it's required that the number of reduce tasks in the Sort Data phase be one more than the number of keys selected in the Range Partitioning step, or else you get an error like this: Caused by: java.lang.IllegalArgumentException: Can't read partitions file at org.apache.hadoop.mapred.lib.TotalOrderPartitioner.configure(TotalOrderPartitioner.java:91) ... 15 more Caused by: java.io.IOException: Wrong number of partitions in keyset at org.apache.hadoop.mapred.lib.TotalOrderPartitioner.configure(TotalOrderPartitioner.java:72) ... 15 more If so, it would be helpful if this was explicitly pointed out. 2. It recommends that you should use the loadtable ruby script to put data into hbase, but if you run this on newer versions of HBase (e.g. 0.90.3) it errors: DISABLED Use completebulkload instead. See tail of http://hbase.apache.org/bulk-loads.html The instructions should probably be changed to use completebulkload instead of this script. -- 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-2590) HBase bulk load wiki page improvements
[ https://issues.apache.org/jira/browse/HIVE-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-2590: Assignee: Ben West HBase bulk load wiki page improvements -- Key: HIVE-2590 URL: https://issues.apache.org/jira/browse/HIVE-2590 Project: Hive Issue Type: Bug Components: Documentation, HBase Handler Reporter: Ben West Assignee: Ben West Priority: Minor Labels: wiki Some suggestions on the page https://cwiki.apache.org/confluence/display/Hive/HBaseBulkLoad which seems kind of out of date: 1. It seems like it's required that the number of reduce tasks in the Sort Data phase be one more than the number of keys selected in the Range Partitioning step, or else you get an error like this: Caused by: java.lang.IllegalArgumentException: Can't read partitions file at org.apache.hadoop.mapred.lib.TotalOrderPartitioner.configure(TotalOrderPartitioner.java:91) ... 15 more Caused by: java.io.IOException: Wrong number of partitions in keyset at org.apache.hadoop.mapred.lib.TotalOrderPartitioner.configure(TotalOrderPartitioner.java:72) ... 15 more If so, it would be helpful if this was explicitly pointed out. 2. It recommends that you should use the loadtable ruby script to put data into hbase, but if you run this on newer versions of HBase (e.g. 0.90.3) it errors: DISABLED Use completebulkload instead. See tail of http://hbase.apache.org/bulk-loads.html The instructions should probably be changed to use completebulkload instead of this script. -- 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-2590) HBase bulk load wiki page improvements
[ https://issues.apache.org/jira/browse/HIVE-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152301#comment-13152301 ] John Sichi commented on HIVE-2590: -- Granted. HBase bulk load wiki page improvements -- Key: HIVE-2590 URL: https://issues.apache.org/jira/browse/HIVE-2590 Project: Hive Issue Type: Bug Components: Documentation, HBase Handler Reporter: Ben West Assignee: Ben West Priority: Minor Labels: wiki Some suggestions on the page https://cwiki.apache.org/confluence/display/Hive/HBaseBulkLoad which seems kind of out of date: 1. It seems like it's required that the number of reduce tasks in the Sort Data phase be one more than the number of keys selected in the Range Partitioning step, or else you get an error like this: Caused by: java.lang.IllegalArgumentException: Can't read partitions file at org.apache.hadoop.mapred.lib.TotalOrderPartitioner.configure(TotalOrderPartitioner.java:91) ... 15 more Caused by: java.io.IOException: Wrong number of partitions in keyset at org.apache.hadoop.mapred.lib.TotalOrderPartitioner.configure(TotalOrderPartitioner.java:72) ... 15 more If so, it would be helpful if this was explicitly pointed out. 2. It recommends that you should use the loadtable ruby script to put data into hbase, but if you run this on newer versions of HBase (e.g. 0.90.3) it errors: DISABLED Use completebulkload instead. See tail of http://hbase.apache.org/bulk-loads.html The instructions should probably be changed to use completebulkload instead of this script. -- 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-2574) ivy offline mode broken by changingPattern and checkmodified attributes
[ https://issues.apache.org/jira/browse/HIVE-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2574: - Fix Version/s: 0.9.0 Status: Patch Available (was: Open) Patch is ready for review. Besides fixing offline mode, it also sets a private resolution cache directory to avoid concurrency problems when running Hive tests in parallel on the same machine. ivy offline mode broken by changingPattern and checkmodified attributes --- Key: HIVE-2574 URL: https://issues.apache.org/jira/browse/HIVE-2574 Project: Hive Issue Type: Bug Reporter: John Sichi Assignee: John Sichi Fix For: 0.9.0 Attachments: HIVE-2574.D435.1.patch, HIVE-2574.D435.2.patch, HIVE-2574.D435.3.patch As described here: http://www.mail-archive.com/ivy-user@ant.apache.org/msg03534.html This wasn't the case formerly (maybe the upgrade to ivy 1.2?) -- 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-2569) Too much debugging info on console if a job failed
[ https://issues.apache.org/jira/browse/HIVE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152397#comment-13152397 ] John Sichi commented on HIVE-2569: -- +1, will commit when tests pass. Too much debugging info on console if a job failed -- Key: HIVE-2569 URL: https://issues.apache.org/jira/browse/HIVE-2569 Project: Hive Issue Type: Improvement Reporter: Ning Zhang Assignee: Ning Zhang Priority: Minor Attachments: D375.1.patch When a job failed and Hive client tries to get the error message from failed task, it printed the following info on console for each task: Examining task ID: task_201110112120_773499_m_37 from job job_201110112120_773499 This should be shorten significantly. -- 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-2523) add a new builtins subproject
[ https://issues.apache.org/jira/browse/HIVE-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2523: - Status: Patch Available (was: Open) Tests passed for me, yay! add a new builtins subproject - Key: HIVE-2523 URL: https://issues.apache.org/jira/browse/HIVE-2523 Project: Hive Issue Type: Improvement Components: UDF Reporter: John Sichi Assignee: John Sichi Fix For: 0.9.0 Attachments: D267.1.patch, D267.2.patch, HIVE-2523.D267.3.patch Now that we have a PDK, we can make it easier to add builtin functions to Hive by putting them in a plugin which automatically gets loaded by Hive. This issue will add the necessary framework and one example function; then new functions can be added here, and over time we could migrate old ones here if desired. -- 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-2593) avoid referencing /tmp in tests
avoid referencing /tmp in tests --- Key: HIVE-2593 URL: https://issues.apache.org/jira/browse/HIVE-2593 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Reporter: John Sichi Assignee: Marek Sapota This is what is causing parallel tests to fail when multiple instances run on the same node. I grepped for /tmp in ql/src/test/queries/clientpositive and the results match the test failures I'm getting. -- 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-2593) avoid referencing /tmp in tests
[
https://issues.apache.org/jira/browse/HIVE-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152491#comment-13152491
]
John Sichi commented on HIVE-2593:
--
We should probably be using ${system:test.tmp.dir} instead.
avoid referencing /tmp in tests
---
Key: HIVE-2593
URL: https://issues.apache.org/jira/browse/HIVE-2593
Project: Hive
Issue Type: Improvement
Components: Testing Infrastructure
Reporter: John Sichi
Assignee: Marek Sapota
This is what is causing parallel tests to fail when multiple instances run on
the same node. I grepped for /tmp in ql/src/test/queries/clientpositive
and the results match the test failures I'm getting.
--
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-2433) add DOAP file for Hive
[ https://issues.apache.org/jira/browse/HIVE-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2433: - Fix Version/s: 0.9.0 Assignee: John Sichi Status: Patch Available (was: Open) add DOAP file for Hive -- Key: HIVE-2433 URL: https://issues.apache.org/jira/browse/HIVE-2433 Project: Hive Issue Type: Sub-task Reporter: John Sichi Assignee: John Sichi Fix For: 0.9.0 Attachments: D333.1.patch, D333.1.patch http://www.apache.org/foundation/marks/pmcs.html#metadata -- 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-2574) ivy offline mode broken by changingPattern and checkmodified attributes
[ https://issues.apache.org/jira/browse/HIVE-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2574: - Attachment: HIVE-2574.D435.3.patch Reattaching latest patch granting ASF rights. ivy offline mode broken by changingPattern and checkmodified attributes --- Key: HIVE-2574 URL: https://issues.apache.org/jira/browse/HIVE-2574 Project: Hive Issue Type: Bug Components: Build Infrastructure Reporter: John Sichi Assignee: John Sichi Fix For: 0.9.0 Attachments: HIVE-2574.D435.1.patch, HIVE-2574.D435.2.patch, HIVE-2574.D435.3.patch, HIVE-2574.D435.3.patch As described here: http://www.mail-archive.com/ivy-user@ant.apache.org/msg03534.html This wasn't the case formerly (maybe the upgrade to ivy 1.2?) -- 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-2523) add a new builtins subproject
[ https://issues.apache.org/jira/browse/HIVE-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13151565#comment-13151565 ] John Sichi commented on HIVE-2523: -- Tests are failing due to a timeout after 5 hours, so I think I must have a leak of some kind...debugging. add a new builtins subproject - Key: HIVE-2523 URL: https://issues.apache.org/jira/browse/HIVE-2523 Project: Hive Issue Type: Improvement Components: UDF Reporter: John Sichi Assignee: John Sichi Fix For: 0.9.0 Attachments: D267.1.patch, D267.2.patch Now that we have a PDK, we can make it easier to add builtin functions to Hive by putting them in a plugin which automatically gets loaded by Hive. This issue will add the necessary framework and one example function; then new functions can be added here, and over time we could migrate old ones here if desired. -- 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-2588) Update arcconfig to include commit listener
[ https://issues.apache.org/jira/browse/HIVE-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2588. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed +1, committed to trunk. Thanks Marek! Update arcconfig to include commit listener --- Key: HIVE-2588 URL: https://issues.apache.org/jira/browse/HIVE-2588 Project: Hive Issue Type: Bug Reporter: Marek Sapota Assignee: Marek Sapota Fix For: 0.9.0 Attachments: HIVE-2588.D477.1.patch Use CommitListener from Arc-JIRA to modify commit message and include `(author via committer)` when running `arc commit`. -- 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-2580) Hive build fails with error java.io.IOException: Not in GZIP format
[ https://issues.apache.org/jira/browse/HIVE-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150707#comment-13150707 ] John Sichi commented on HIVE-2580: -- Committed to trunk. Carl, can you include this in your 0.8 backport for HIVE-2391 so we can mark both of these resolved? Hive build fails with error java.io.IOException: Not in GZIP format - Key: HIVE-2580 URL: https://issues.apache.org/jira/browse/HIVE-2580 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.8.0 Reporter: Carl Steinbach Assignee: Carl Steinbach Priority: Blocker Fix For: 0.8.0 Attachments: HIVE-2580.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] [Resolved] (HIVE-2583) bug in ivy 2.2.0 breaks build
[ https://issues.apache.org/jira/browse/HIVE-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2583. -- Resolution: Duplicate Dupe of HIVE-2580. bug in ivy 2.2.0 breaks build - Key: HIVE-2583 URL: https://issues.apache.org/jira/browse/HIVE-2583 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.8.0 Reporter: Francis Liu Fix For: 0.8.0 there seems to be a bug in ivy 2.2.0 which causes downloaded .tar.gz files getting uncompressed but left tar'd rather than just being downloaded. Forcing online ivy update by using a new cache: ant -Divy.default.ivy.user.dir=/tmp/my_ivy_cache clean jar will yield this build failure: BUILD FAILED /Users/fcliu/dev/IdeaProjects/hive/build.xml:297: The following error occurred while executing this line: /Users/fcliu/dev/IdeaProjects/hive/build.xml:154: The following error occurred while executing this line: /Users/fcliu/dev/IdeaProjects/hive/shims/build.xml:65: The following error occurred while executing this line: /Users/fcliu/dev/IdeaProjects/hive/build-common.xml:132: Error while expanding /Users/fcliu/dev/IdeaProjects/hive/build/hadoopcore/hadoop-0.20.1.tar.gz java.io.IOException: Not in GZIP format at java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:143) at java.util.zip.GZIPInputStream.init(GZIPInputStream.java:58) at java.util.zip.GZIPInputStream.init(GZIPInputStream.java:67) at org.apache.tools.ant.taskdefs.Untar$UntarCompressionMethod.decompress(Untar.java:235) at org.apache.tools.ant.taskdefs.Untar.expandStream(Untar.java:158) at org.apache.tools.ant.taskdefs.Untar.expandFile(Untar.java:114) at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:132) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.Target.performTasks(Target.java:411) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.Target.performTasks(Target.java:411) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442) at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:302) at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:221) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348
[jira] [Commented] (HIVE-2580) Hive build fails with error java.io.IOException: Not in GZIP format
[ https://issues.apache.org/jira/browse/HIVE-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150198#comment-13150198 ] John Sichi commented on HIVE-2580: -- +1, will commit when tests pass. Hive build fails with error java.io.IOException: Not in GZIP format - Key: HIVE-2580 URL: https://issues.apache.org/jira/browse/HIVE-2580 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.8.0 Reporter: Carl Steinbach Assignee: Carl Steinbach Priority: Blocker Fix For: 0.8.0 Attachments: HIVE-2580.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-2532) Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned.
[ https://issues.apache.org/jira/browse/HIVE-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148686#comment-13148686 ] John Sichi commented on HIVE-2532: -- +1, tests passed. Can you grant ASF rights? Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned. Key: HIVE-2532 URL: https://issues.apache.org/jira/browse/HIVE-2532 Project: Hive Issue Type: Bug Reporter: Jonathan Chang Assignee: Jonathan Chang Attachments: D273.1.patch, D273.2.patch, D273.3.patch, D273.4.patch Even if constant oi is returned, these may have stateful/side-effect behavior and hence need to be called each cycle. -- 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-2532) Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned.
[ https://issues.apache.org/jira/browse/HIVE-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2532. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Committed to trunk, thanks Jonathan! Also don't forget to update the wiki. Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned. Key: HIVE-2532 URL: https://issues.apache.org/jira/browse/HIVE-2532 Project: Hive Issue Type: Bug Reporter: Jonathan Chang Assignee: Jonathan Chang Fix For: 0.9.0 Attachments: D273.1.patch, D273.2.patch, D273.3.patch, D273.4.patch, D273.4.patch, D273.4.patch Even if constant oi is returned, these may have stateful/side-effect behavior and hence need to be called each cycle. -- 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-1040) use sed rather than diff for masking out noise in diff-based tests
[ https://issues.apache.org/jira/browse/HIVE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-1040: Assignee: Marek Sapota use sed rather than diff for masking out noise in diff-based tests -- Key: HIVE-1040 URL: https://issues.apache.org/jira/browse/HIVE-1040 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Affects Versions: 0.4.1 Reporter: John Sichi Assignee: Marek Sapota Priority: Minor The current diff -I approach has two problems: (1) it does not allow resolution finer than line-level, so it's impossible to mask out pattern occurrences within a line, and (2) it produces unmasked files, so if you run diff on the command line to compare the result .q.out with the checked-in file, you see the noise. My suggestion is to first run sed to replace noise patterns with an unlikely-to-occur string like ZYZZYZVA, and then diff the pre-masked files without using any -I. This would require a one-time hit to update all existing .q.out files so that they would contain the pre-masked results. -- 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-1040) use sed rather than diff for masking out noise in diff-based tests
[ https://issues.apache.org/jira/browse/HIVE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148727#comment-13148727 ] John Sichi commented on HIVE-1040: -- Observation from Marek: also, if we include a snippet of the diff (maybe first 20 lines?) in the junit test report, that would be really useful. We don't want to include the whole thing since it can be huge. use sed rather than diff for masking out noise in diff-based tests -- Key: HIVE-1040 URL: https://issues.apache.org/jira/browse/HIVE-1040 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Affects Versions: 0.4.1 Reporter: John Sichi Priority: Minor The current diff -I approach has two problems: (1) it does not allow resolution finer than line-level, so it's impossible to mask out pattern occurrences within a line, and (2) it produces unmasked files, so if you run diff on the command line to compare the result .q.out with the checked-in file, you see the noise. My suggestion is to first run sed to replace noise patterns with an unlikely-to-occur string like ZYZZYZVA, and then diff the pre-masked files without using any -I. This would require a one-time hit to update all existing .q.out files so that they would contain the pre-masked results. -- 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-2449) streamline .q.out format
[ https://issues.apache.org/jira/browse/HIVE-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-2449: Assignee: Marek Sapota streamline .q.out format Key: HIVE-2449 URL: https://issues.apache.org/jira/browse/HIVE-2449 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Reporter: John Sichi Assignee: Marek Sapota Currently, we enable all available testing hooks (e.g. lineage, input/output) for all tests. This creates a huge amount of noise in the .q.out files, making it very difficult to read them and to review diffs in them. To fix this, we should only selectively enable specific hooks for specific tests where the coverage is needed. Undertaking this will necessitate a one-time hit for updating all existing .q.out files. Probably best to do together with HIVE-1040. -- 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-2574) ivy offline mode broken by changingPattern and checkmodified attributes
ivy offline mode broken by changingPattern and checkmodified attributes --- Key: HIVE-2574 URL: https://issues.apache.org/jira/browse/HIVE-2574 Project: Hive Issue Type: Bug Reporter: John Sichi Assignee: John Sichi As described here: http://www.mail-archive.com/ivy-user@ant.apache.org/msg03534.html This wasn't the case formerly (maybe the upgrade to ivy 1.2?) -- 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
Fwd: [DISCUSSION]: Synchronizing HCatalog and Hive trees
FYI Begin forwarded message: From: Olga Natkovich ol...@yahoo-inc.com Date: November 9, 2011 2:54:14 PM PST To: hcatalog-...@incubator.apache.org hcatalog-...@incubator.apache.org Subject: [DISCUSSION]: Synchronizing HCatalog and Hive trees Reply-To: hcatalog-...@incubator.apache.org Hi, Since HCatalog has dependencies on Hive source tree we need to figure out how to stay in synch with Hive source while not having to deal with random build/test failures on a regular basis. Here is the proposal: (1)During normal development cycle, HCatalog trunk would use a particular revision of Hive to build against (2)Any time a change from Hive is needed by Hcatalog, the revision number will move forward. The developer who is brining this change into Hcatalog is responsible for making sure that the build is stable before moving the extern tag (3)As part of the HCatalog release process, prior to branching for the release, HCatalog will be integrated with the latest Hive code. a. This could be the latest Hive release if it contains all the changes required for Hcatalog or the latest Hive trunk otherwise b. Developer responsible for branching for the release is responsible for stabilizing the build with the latest Hive code prior to branching. Once the stabilization is done, a tag is created in Hive and the release branch uses that tag for all builds c. If later on a problem is found with this tag, Hive code would be branched on the tag and necessary bug fixes applied. Comments? Olga
[jira] [Commented] (HIVE-2565) Add Java linter to Hive
[ https://issues.apache.org/jira/browse/HIVE-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13147359#comment-13147359 ] John Sichi commented on HIVE-2565: -- +1, committed to trunk. Thanks Marek! Add Java linter to Hive --- Key: HIVE-2565 URL: https://issues.apache.org/jira/browse/HIVE-2565 Project: Hive Issue Type: Bug Reporter: Marek Sapota Assignee: Marek Sapota Attachments: D345.1.patch Add a linter that will be run at `arc diff` and will check for too long lines, trailing whitespace, etc. -- 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-2478) Support dry run option in hive
[ https://issues.apache.org/jira/browse/HIVE-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13146486#comment-13146486 ] John Sichi commented on HIVE-2478: -- Yes, it does execute user-defined code, e.g. for resolving the types of UDF invocations. Without that, you'd have to stop immediately after ANTLR parsing (pure syntax check, no semantic analysis). Support dry run option in hive -- Key: HIVE-2478 URL: https://issues.apache.org/jira/browse/HIVE-2478 Project: Hive Issue Type: Improvement Components: Configuration Affects Versions: 0.9.0 Reporter: kalyan ram Priority: Minor Attachments: HIVE-2478-1.patch Hive currently doesn't support a dry run option. For some complex queries we just want to verify the query syntax initally before running it. A dry run option where just the parsing is done without actual execution is a good option. -- 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-2391) published POMs in Maven repo are incorrect
[ https://issues.apache.org/jira/browse/HIVE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13146488#comment-13146488 ] John Sichi commented on HIVE-2391: -- OK, +1, committed to trunk. I'll leave this open and you can mark it resolved once you commit the backport? published POMs in Maven repo are incorrect -- Key: HIVE-2391 URL: https://issues.apache.org/jira/browse/HIVE-2391 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.7.1 Reporter: Alejandro Abdelnur Assignee: Carl Steinbach Priority: Critical Fix For: 0.8.0 Attachments: HIVE-2391.1.patch.txt, HIVE-2391.2.patch.txt, HIVE-2391.3.patch.txt, HIVE-2391.4.patch.txt, HIVE-2391.5.patch.txt, HIVE-2391.wip.1.patch.txt The Hive artifacts published in Apache Maven SNAPSHOTS repo are incorrect. Dependencies are not complete. Even after adding as dependencies ALL the Hive artifacts it is not possible to compile a project using Hive JARs (I'm trying to integrate Oozie Hive Action using Apache Hive). As a reference the Hive CDH POMs dependencies could be used (Using those artifacts I'm able to compile/test/run Hive from within Oozie). -- 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-2434) add a TM to Hive logo image
[ https://issues.apache.org/jira/browse/HIVE-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2434: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pure awesomeness. add a TM to Hive logo image --- Key: HIVE-2434 URL: https://issues.apache.org/jira/browse/HIVE-2434 Project: Hive Issue Type: Sub-task Reporter: John Sichi Assignee: Charles Chen Attachments: hive job tracker icons (font outlines)-withtm.pdf, hive_logo_medium.jpg, hive_logo_medium.pdf http://www.apache.org/foundation/marks/pmcs.html#graphics And maybe the feather? -- 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-1434) Cassandra Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-1434: - Status: Open (was: Patch Available) Cassandra Storage Handler - Key: HIVE-1434 URL: https://issues.apache.org/jira/browse/HIVE-1434 Project: Hive Issue Type: New Feature Affects Versions: 0.7.0 Reporter: Edward Capriolo Assignee: Edward Capriolo Attachments: HIVE-1434-r1182878.patch, cas-handle.tar.gz, cass_handler.diff, hive-1434-1.txt, hive-1434-2-patch.txt, hive-1434-2011-02-26.patch.txt, hive-1434-2011-03-07.patch.txt, hive-1434-2011-03-07.patch.txt, hive-1434-2011-03-14.patch.txt, hive-1434-3-patch.txt, hive-1434-4-patch.txt, hive-1434-5.patch.txt, hive-1434.2011-02-27.diff.txt, hive-cassandra.2011-02-25.txt, hive.diff Add a cassandra storage handler. -- 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-2548) How to submit documentation fixes
[ https://issues.apache.org/jira/browse/HIVE-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2548: - Resolution: Fixed Status: Resolved (was: Patch Available) How to submit documentation fixes - Key: HIVE-2548 URL: https://issues.apache.org/jira/browse/HIVE-2548 Project: Hive Issue Type: Bug Components: Documentation Affects Versions: 0.7.1 Environment: general linux Reporter: Stephen Boesch Assignee: Stephen Boesch Priority: Minor Fix For: 0.8.0 Original Estimate: 1h Remaining Estimate: 1h I am walking through the developer's guide and tutorial and finding issues: e.g. broken links. Is there a way to try out updates to the docs and submit patches? Here is the first example on https://cwiki.apache.org/Hive/tutorial.html The following examples highlight some salient features of the system. A detailed set of query test cases can be found at Hive Query Test Cases and the corresponding results can be found at Query Test Case Results. The first link is listed as http://svn.apache.org/viewvc/hadoop/hive/trunk/ql/src/test/queries/clientpositive/ Second link is http://svn.apache.org/viewvc/hadoop/hive/trunk/ql/src/test/results/clientpositive/ Both links are 404's -- 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-2547) Tiny bug in init-hive-dfs.sh
[ https://issues.apache.org/jira/browse/HIVE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2547: - Status: Open (was: Patch Available) Tiny bug in init-hive-dfs.sh - Key: HIVE-2547 URL: https://issues.apache.org/jira/browse/HIVE-2547 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.8.0 Environment: ubuntu / general linux Reporter: Stephen Boesch Assignee: Stephen Boesch Priority: Minor Labels: initialization Fix For: 0.8.0 Original Estimate: 5m Remaining Estimate: 5m init-hive-dfs.sh seems to have a small typo on line 73 in which it requests $HADOOP instead of $HADOOP_EXEC -- 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-2560) speed up Hive unit tests by configuring Derby to be non-durable
speed up Hive unit tests by configuring Derby to be non-durable --- Key: HIVE-2560 URL: https://issues.apache.org/jira/browse/HIVE-2560 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Affects Versions: 0.9.0 Reporter: John Sichi Assignee: Marek Sapota Try setting derby.system.durability=test to see if it can speed up metastore writes while running Hive ant test. http://db.apache.org/derby/docs/10.1/tuning/rtunproperdurability.html -- 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-2478) Support dry run option in hive
[
https://issues.apache.org/jira/browse/HIVE-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13146571#comment-13146571
]
John Sichi commented on HIVE-2478:
--
If we're going to add this, it would be best to generalize it so that you can
choose what phase to stop after, e.g.
hive.exec.dryrun={off,parse,analyze,plan}
Support dry run option in hive
--
Key: HIVE-2478
URL: https://issues.apache.org/jira/browse/HIVE-2478
Project: Hive
Issue Type: Improvement
Components: Configuration
Affects Versions: 0.9.0
Reporter: kalyan ram
Priority: Minor
Attachments: HIVE-2478-1.patch, HIVE-2478-2.patch
Hive currently doesn't support a dry run option. For some complex queries we
just want to verify the query syntax initally before running it. A dry run
option where just the parsing is done without actual execution is a good
option.
--
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-2560) speed up Hive unit tests by configuring Derby to be non-durable
[ https://issues.apache.org/jira/browse/HIVE-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2560. -- Resolution: Invalid Closing this as invalid since my guess on its usefulness was wrong. speed up Hive unit tests by configuring Derby to be non-durable --- Key: HIVE-2560 URL: https://issues.apache.org/jira/browse/HIVE-2560 Project: Hive Issue Type: Improvement Components: Testing Infrastructure Affects Versions: 0.9.0 Reporter: John Sichi Assignee: Marek Sapota Attachments: D327.1.patch, D327.2.patch, D327.3.patch Try setting derby.system.durability=test to see if it can speed up metastore writes while running Hive ant test. http://db.apache.org/derby/docs/10.1/tuning/rtunproperdurability.html -- 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-2433) add DOAP file for Hive
[ https://issues.apache.org/jira/browse/HIVE-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2433: - Attachment: D333.1.patch add DOAP file for Hive -- Key: HIVE-2433 URL: https://issues.apache.org/jira/browse/HIVE-2433 Project: Hive Issue Type: Sub-task Reporter: John Sichi Attachments: D333.1.patch, D333.1.patch http://www.apache.org/foundation/marks/pmcs.html#metadata -- 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-2391) published POMs in Maven repo are incorrect
[ https://issues.apache.org/jira/browse/HIVE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145781#comment-13145781 ] John Sichi commented on HIVE-2391: -- Tests passed cleanly on trunk. I tried applying HIVE-2391.5.patch.txt on 0.8 and got conflicts; Carl, do you want to give me a backport for that and then I can commit both? published POMs in Maven repo are incorrect -- Key: HIVE-2391 URL: https://issues.apache.org/jira/browse/HIVE-2391 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.7.1 Reporter: Alejandro Abdelnur Assignee: Carl Steinbach Priority: Critical Fix For: 0.8.0 Attachments: HIVE-2391.1.patch.txt, HIVE-2391.2.patch.txt, HIVE-2391.3.patch.txt, HIVE-2391.4.patch.txt, HIVE-2391.5.patch.txt, HIVE-2391.wip.1.patch.txt The Hive artifacts published in Apache Maven SNAPSHOTS repo are incorrect. Dependencies are not complete. Even after adding as dependencies ALL the Hive artifacts it is not possible to compile a project using Hive JARs (I'm trying to integrate Oozie Hive Action using Apache Hive). As a reference the Hive CDH POMs dependencies could be used (Using those artifacts I'm able to compile/test/run Hive from within Oozie). -- 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-2527) Consecutive string literals should be combined into a single string literal.
[ https://issues.apache.org/jira/browse/HIVE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145784#comment-13145784 ] John Sichi commented on HIVE-2527: -- I'll rerun tests with latest. Consecutive string literals should be combined into a single string literal. Key: HIVE-2527 URL: https://issues.apache.org/jira/browse/HIVE-2527 Project: Hive Issue Type: Improvement Reporter: Jonathan Chang Assignee: Jonathan Chang Priority: Minor Attachments: D147.1.patch, D147.2.patch, D147.3.patch, D147.3.patch, D147.4.patch C, Python, etc. all support this magical feature. -- 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-2547) Tiny bug in init-hive-dfs.sh
[ https://issues.apache.org/jira/browse/HIVE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145867#comment-13145867 ] John Sichi commented on HIVE-2547: -- Marek said that the github.com URL redirects to nodeload.github.com automatically, so we should leave it as github.com since that's the official one. Tiny bug in init-hive-dfs.sh - Key: HIVE-2547 URL: https://issues.apache.org/jira/browse/HIVE-2547 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.8.0 Environment: ubuntu / general linux Reporter: Stephen Boesch Assignee: Stephen Boesch Priority: Minor Labels: initialization Fix For: 0.8.0 Original Estimate: 5m Remaining Estimate: 5m init-hive-dfs.sh seems to have a small typo on line 73 in which it requests $HADOOP instead of $HADOOP_EXEC -- 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-2527) Consecutive string literals should be combined into a single string literal.
[ https://issues.apache.org/jira/browse/HIVE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2527. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Committed to trunk. Thanks Jonathan! Can you reattach the last patch with ASF grant? Consecutive string literals should be combined into a single string literal. Key: HIVE-2527 URL: https://issues.apache.org/jira/browse/HIVE-2527 Project: Hive Issue Type: Improvement Reporter: Jonathan Chang Assignee: Jonathan Chang Priority: Minor Fix For: 0.9.0 Attachments: D147.1.patch, D147.2.patch, D147.3.patch, D147.3.patch, D147.4.patch C, Python, etc. all support this magical feature. -- 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-2391) published POMs in Maven repo are incorrect
[ https://issues.apache.org/jira/browse/HIVE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145117#comment-13145117 ] John Sichi commented on HIVE-2391: -- Running through tests again now. published POMs in Maven repo are incorrect -- Key: HIVE-2391 URL: https://issues.apache.org/jira/browse/HIVE-2391 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.7.1 Reporter: Alejandro Abdelnur Assignee: Carl Steinbach Priority: Critical Fix For: 0.8.0 Attachments: HIVE-2391.1.patch.txt, HIVE-2391.2.patch.txt, HIVE-2391.3.patch.txt, HIVE-2391.4.patch.txt, HIVE-2391.5.patch.txt, HIVE-2391.wip.1.patch.txt The Hive artifacts published in Apache Maven SNAPSHOTS repo are incorrect. Dependencies are not complete. Even after adding as dependencies ALL the Hive artifacts it is not possible to compile a project using Hive JARs (I'm trying to integrate Oozie Hive Action using Apache Hive). As a reference the Hive CDH POMs dependencies could be used (Using those artifacts I'm able to compile/test/run Hive from within Oozie). -- 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-1690) HivePreparedStatement.executeImmediate(String sql) is breaking the exception stack
[ https://issues.apache.org/jira/browse/HIVE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-1690: - Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to trunk. Thanks Ashutosh! HivePreparedStatement.executeImmediate(String sql) is breaking the exception stack -- Key: HIVE-1690 URL: https://issues.apache.org/jira/browse/HIVE-1690 Project: Hive Issue Type: Improvement Components: JDBC Reporter: Eli Griv Assignee: Ashutosh Chauhan Priority: Minor Fix For: 0.9.0 Attachments: hive-1690.patch in HivePreparedStatement.executeImmediate(String sql), the exception stack is broken, so it's impossible to know which method throwed Method not supported FIX : HivePreparedStatement.java L166 - throw new SQLException(e.getMessage(), e.getSQLState(), e.getErrorCode()); + throw new SQLException(e.getMessage(), e.getSQLState(), e.getErrorCode(), e); L168 - throw new SQLException(ex.toString(), 08S01); + throw new SQLException(ex.toString(), 08S01, ex); -- 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-2550) Provide jira_base_url for improved arc commit workflow
[ https://issues.apache.org/jira/browse/HIVE-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2550. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Committed to trunk. Thanks Marek! Provide jira_base_url for improved arc commit workflow -- Key: HIVE-2550 URL: https://issues.apache.org/jira/browse/HIVE-2550 Project: Hive Issue Type: Bug Reporter: Marek Sapota Fix For: 0.9.0 Attachments: D249.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] [Commented] (HIVE-2529) metastore 0.8 upgrade script for PostgreSQL
[ https://issues.apache.org/jira/browse/HIVE-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13144409#comment-13144409 ] John Sichi commented on HIVE-2529: -- Fine with me; but isn't it a little confusing to have the existing scripts checked in then? Should they move to contrib? metastore 0.8 upgrade script for PostgreSQL Key: HIVE-2529 URL: https://issues.apache.org/jira/browse/HIVE-2529 Project: Hive Issue Type: Improvement Components: Metastore Affects Versions: 0.8.0 Reporter: John Sichi Assignee: Carl Steinbach Priority: Blocker I think you mentioned that this was in the works. -- 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-2529) metastore 0.8 upgrade script for PostgreSQL
[ https://issues.apache.org/jira/browse/HIVE-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13144410#comment-13144410 ] John Sichi commented on HIVE-2529: -- (or should we just change the build to omit them from the release?) metastore 0.8 upgrade script for PostgreSQL Key: HIVE-2529 URL: https://issues.apache.org/jira/browse/HIVE-2529 Project: Hive Issue Type: Improvement Components: Metastore Affects Versions: 0.8.0 Reporter: John Sichi Assignee: Carl Steinbach Priority: Blocker I think you mentioned that this was in the works. -- 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-11) better error code from Hive describe command
[ https://issues.apache.org/jira/browse/HIVE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-11: --- Status: Open (was: Patch Available) Existing negative test cases external1.q and external2.q are now failing; they need .q.out updates. better error code from Hive describe command Key: HIVE-11 URL: https://issues.apache.org/jira/browse/HIVE-11 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.6.0, 0.5.0, 0.4.1, 0.4.0, 0.3.0, 0.8.0, 0.9.0 Reporter: Joydeep Sen Sarma Assignee: Ashutosh Chauhan Fix For: 0.9.0 Attachments: hive-11.patch, hive-11_1.patch cryptic, non-informative error message hive describe hive1_scribeloadertest FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask in this case the table was missing. better say 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] [Commented] (HIVE-2548) How to submit documentation fixes
[ https://issues.apache.org/jira/browse/HIVE-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13143444#comment-13143444 ] John Sichi commented on HIVE-2548: -- Create an account in the wiki, and let me know the username; then I'll grant you edit privileges and you can fix it. How to submit documentation fixes - Key: HIVE-2548 URL: https://issues.apache.org/jira/browse/HIVE-2548 Project: Hive Issue Type: Bug Components: Documentation Affects Versions: 0.7.1 Environment: general linux Reporter: Stephen Boesch Assignee: Stephen Boesch Priority: Minor Fix For: 0.8.0 Original Estimate: 1h Remaining Estimate: 1h I am walking through the developer's guide and tutorial and finding issues: e.g. broken links. Is there a way to try out updates to the docs and submit patches? Here is the first example on https://cwiki.apache.org/Hive/tutorial.html The following examples highlight some salient features of the system. A detailed set of query test cases can be found at Hive Query Test Cases and the corresponding results can be found at Query Test Case Results. The first link is listed as http://svn.apache.org/viewvc/hadoop/hive/trunk/ql/src/test/queries/clientpositive/ Second link is http://svn.apache.org/viewvc/hadoop/hive/trunk/ql/src/test/results/clientpositive/ Both links are 404's -- 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-2548) How to submit documentation fixes
[ https://issues.apache.org/jira/browse/HIVE-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-2548: Assignee: Stephen Boesch How to submit documentation fixes - Key: HIVE-2548 URL: https://issues.apache.org/jira/browse/HIVE-2548 Project: Hive Issue Type: Bug Components: Documentation Affects Versions: 0.7.1 Environment: general linux Reporter: Stephen Boesch Assignee: Stephen Boesch Priority: Minor Fix For: 0.8.0 Original Estimate: 1h Remaining Estimate: 1h I am walking through the developer's guide and tutorial and finding issues: e.g. broken links. Is there a way to try out updates to the docs and submit patches? Here is the first example on https://cwiki.apache.org/Hive/tutorial.html The following examples highlight some salient features of the system. A detailed set of query test cases can be found at Hive Query Test Cases and the corresponding results can be found at Query Test Case Results. The first link is listed as http://svn.apache.org/viewvc/hadoop/hive/trunk/ql/src/test/queries/clientpositive/ Second link is http://svn.apache.org/viewvc/hadoop/hive/trunk/ql/src/test/results/clientpositive/ Both links are 404's -- 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-2547) Tiny bug in init-hive-dfs.sh
[ https://issues.apache.org/jira/browse/HIVE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-2547: Assignee: Stephen Boesch Tiny bug in init-hive-dfs.sh - Key: HIVE-2547 URL: https://issues.apache.org/jira/browse/HIVE-2547 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.8.0 Environment: ubuntu / general linux Reporter: Stephen Boesch Assignee: Stephen Boesch Priority: Minor Labels: initialization Fix For: 0.8.0 Original Estimate: 5m Remaining Estimate: 5m init-hive-dfs.sh seems to have a small typo on line 73 in which it requests $HADOOP instead of $HADOOP_EXEC -- 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-2547) Tiny bug in init-hive-dfs.sh
[ https://issues.apache.org/jira/browse/HIVE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13143447#comment-13143447 ] John Sichi commented on HIVE-2547: -- Here are the instructions for submitting patches: https://cwiki.apache.org/confluence/display/Hive/PhabricatorCodeReview (Also, Attach Files is now under More Actions above in JIRA.) Tiny bug in init-hive-dfs.sh - Key: HIVE-2547 URL: https://issues.apache.org/jira/browse/HIVE-2547 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.8.0 Environment: ubuntu / general linux Reporter: Stephen Boesch Assignee: Stephen Boesch Priority: Minor Labels: initialization Fix For: 0.8.0 Original Estimate: 5m Remaining Estimate: 5m init-hive-dfs.sh seems to have a small typo on line 73 in which it requests $HADOOP instead of $HADOOP_EXEC -- 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-2214) CommandNeedRetryException.java is missing ASF header
[ https://issues.apache.org/jira/browse/HIVE-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13143451#comment-13143451 ] John Sichi commented on HIVE-2214: -- +1, will commit. CommandNeedRetryException.java is missing ASF header Key: HIVE-2214 URL: https://issues.apache.org/jira/browse/HIVE-2214 Project: Hive Issue Type: Bug Affects Versions: 0.8.0 Reporter: John Sichi Assignee: Siying Dong Fix For: 0.8.0 Attachments: hive-2214.patch Please add one. -- 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-1496) enhance CREATE INDEX to support immediate index build
[ https://issues.apache.org/jira/browse/HIVE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13143475#comment-13143475 ] John Sichi commented on HIVE-1496: -- Oof. That sounds too painful+brittle. What if we instead prepare a reentrant CREATE TABLE AS SELECT statement (rather than an INSERT statement), but then splice out the CREATE TABLE part (leaving just the load part). Still very hacky, but maybe not too much. enhance CREATE INDEX to support immediate index build - Key: HIVE-1496 URL: https://issues.apache.org/jira/browse/HIVE-1496 Project: Hive Issue Type: Improvement Components: Indexing Affects Versions: 0.7.0, 0.8.0 Reporter: John Sichi Assignee: Syed S. Albiz Attachments: hive-1496.patch Currently we only support WITH DEFERRED REBUILD. -- 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-2467) HA Support for Metastore Server
[ https://issues.apache.org/jira/browse/HIVE-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-2467: Assignee: Thomas Weise HA Support for Metastore Server Key: HIVE-2467 URL: https://issues.apache.org/jira/browse/HIVE-2467 Project: Hive Issue Type: Improvement Components: Metastore Affects Versions: 0.8.0, 0.9.0 Reporter: Thomas Weise Assignee: Thomas Weise Fix For: 0.9.0 Attachments: HIVE-2467.patch We require HA deployment for metastore server for HCatalog: * Multiple server instances run behind VIP * Database provides HA Metastore server instances will need to be able to share any state required for VIP outside RDBMS. As of Hive 0.8 affected conversational state that needs to support VIP/HA setup is limited to current delegation tokens. Is this correct? We are planning to use ZooKeeper to share current delegation tokens and master keys between nodes of the VIP. ZK is already (optionally) used by Hive for concurrency control. Access to ZK would be limited on the network level or in the future, when ZooKeeper supports security, through Kerberos, similar to NN access. Currently Hive taps into Hadoop core security delegation token support through extension of org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManagerTokenIdent A solution could amend the Hive specific extension to support: * Pluggable delegation token and master key store (ZooKeeper as alternative for in-memory AbstractDelegationTokenSecretManager) * Delegation token retrieval from token store when not found in memory (wrap/extend retrievePassword(...)) * Cancellation of token in token store * Purging of expired tokens from token store http://www.mail-archive.com/hcatalog-user@incubator.apache.org/msg00053.html -- 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-1496) enhance CREATE INDEX to support immediate index build
[ https://issues.apache.org/jira/browse/HIVE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141646#comment-13141646 ] John Sichi commented on HIVE-1496: -- @Syed: how does CREATE TABLE AS SELECT manage to do it? Doesn't it need to prepare the equivalent of an INSERT statement against a table which doesn't exist yet? enhance CREATE INDEX to support immediate index build - Key: HIVE-1496 URL: https://issues.apache.org/jira/browse/HIVE-1496 Project: Hive Issue Type: Improvement Components: Indexing Affects Versions: 0.7.0, 0.8.0 Reporter: John Sichi Assignee: Syed S. Albiz Attachments: hive-1496.patch Currently we only support WITH DEFERRED REBUILD. -- 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-2527) Consecutive string literals should be combined into a single string literal.
[
https://issues.apache.org/jira/browse/HIVE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141664#comment-13141664
]
John Sichi commented on HIVE-2527:
--
Got all kinds of failures, e.g. this one from dboutput.q in
TestContribCliDriver:
{noformat}
[junit] diff -a -I file: -I pfile: -I hdfs: -I /tmp/ -I invalidscheme: -I
lastUp
dateTime -I lastAccessTime -I [Oo]wner -I CreateTime -I LastAccessTime -I
Location -
I LOCATION ' -I transient_lastDdlTime -I last_modified_ -I
java.lang.RuntimeExceptio
n -I at org -I at sun -I at java -I at junit -I Caused by: -I LOCK_QUERYID: -I
LOCK_
TIME: -I grantTime -I [.][.][.] [0-9]* more -I job_[0-9]*_[0-9]* -I USING 'java
-cp
/data/users/jsichi/open/test-trunk/build/contrib/test/logs/contribclientpositive/dbo
utput.q.out
/data/users/jsichi/open/test-trunk/contrib/src/test/results/clientpositi
ve/dboutput.q.out
[junit] 48c48
[junit](TOK_QUERY (TOK_FROM (TOK_TABREF (TOK_TABNAME src)))
(TOK_INSERT (TO
K_DESTINATION (TOK_DIR TOK_TMP_FILE)) (TOK_SELECT (TOK_SELEXPR (TOK_FUNCTION
dboutpu
t (TOK_STRINGLITERALSEQUENCE
'jdbc:derby:../build/test_dboutput_db;create=true') (TO
K_STRINGLITERALSEQUENCE '') (TOK_STRINGLITERALSEQUENCE '')
(TOK_STRINGLITERALSEQUENC
E 'CREATE TABLE app_info ( kkey VARCHAR(255) NOT NULL, vvalue VARCHAR(255) NOT
NULL,
UNIQUE(kkey))'))) (TOK_SELEXPR (TOK_FUNCTION dboutput
(TOK_STRINGLITERALSEQUENCE 'j
dbc:derby:../build/test_dboutput_db') (TOK_STRINGLITERALSEQUENCE '')
(TOK_STRINGLITE
RALSEQUENCE '') (TOK_STRINGLITERALSEQUENCE 'INSERT INTO app_info (kkey,vvalue)
VALUE
S (?,?)') (TOK_STRINGLITERALSEQUENCE '20') (TOK_STRINGLITERALSEQUENCE 'a')))
(TOK_SE
LEXPR (TOK_FUNCTION dboutput (TOK_STRINGLITERALSEQUENCE
'jdbc:derby:../build/test_db
output_db') (TOK_STRINGLITERALSEQUENCE '') (TOK_STRINGLITERALSEQUENCE '')
(TOK_STRIN
GLITERALSEQUENCE 'INSERT INTO app_info (kkey,vvalue) VALUES (?,?)')
(TOK_STRINGLITER
ALSEQUENCE '20') (TOK_STRINGLITERALSEQUENCE 'b' (TOK_LIMIT 1)))
[junit] ---
[junit](TOK_QUERY (TOK_FROM (TOK_TABREF (TOK_TABNAME src)))
(TOK_INSERT (TO
K_DESTINATION (TOK_DIR TOK_TMP_FILE)) (TOK_SELECT (TOK_SELEXPR (TOK_FUNCTION
dboutpu
t 'jdbc:derby:../build/test_dboutput_db;create=true' '' '' 'CREATE TABLE
app_info (
kkey VARCHAR(255) NOT NULL, vvalue VARCHAR(255) NOT NULL, UNIQUE(kkey))'))
(TOK_SELE
XPR (TOK_FUNCTION dboutput 'jdbc:derby:../build/test_dboutput_db' '' '' 'INSERT
INTO
app_info (kkey,vvalue) VALUES (?,?)' '20' 'a')) (TOK_SELEXPR (TOK_FUNCTION
dboutput
'jdbc:derby:../build/test_dboutput_db' '' '' 'INSERT INTO app_info
(kkey,vvalue) VA
LUES (?,?)' '20' 'b'))) (TOK_LIMIT 1)))
[junit] 129c129
[junit](TOK_QUERY (TOK_FROM (TOK_TABREF (TOK_TABNAME src)))
(TOK_INSERT (TO
K_DESTINATION (TOK_DIR TOK_TMP_FILE)) (TOK_SELECT (TOK_SELEXPR (TOK_FUNCTION
dboutpu
t (TOK_STRINGLITERALSEQUENCE 'jdbc:derby:../build/test_dboutput_db')
(TOK_STRINGLITE
RALSEQUENCE '') (TOK_STRINGLITERALSEQUENCE '') (TOK_STRINGLITERALSEQUENCE
'INSERT IN
TO app_info (kkey,vvalue) VALUES (?,?)') (TOK_TABLE_OR_COL key)
(TOK_TABLE_OR_COL va
lue (TOK_WHERE ( (TOK_TABLE_OR_COL key) 10
[junit] ---
[junit](TOK_QUERY (TOK_FROM (TOK_TABREF (TOK_TABNAME src)))
(TOK_INSERT (TO
K_DESTINATION (TOK_DIR TOK_TMP_FILE)) (TOK_SELECT (TOK_SELEXPR (TOK_FUNCTION
dboutpu
t 'jdbc:derby:../build/test_dboutput_db' '' '' 'INSERT INTO app_info
(kkey,vvalue) V
ALUES (?,?)' (TOK_TABLE_OR_COL key) (TOK_TABLE_OR_COL value (TOK_WHERE (
(TOK_T
ABLE_OR_COL key) 10
[junit] Exception: Client execution results failed with error code = 1
[junit] See build/ql/tmp/hive.log, or try ant test ...
-Dtest.silent=false to
get more logs.
{noformat}
Consecutive string literals should be combined into a single string literal.
Key: HIVE-2527
URL: https://issues.apache.org/jira/browse/HIVE-2527
Project: Hive
Issue Type: Improvement
Reporter: Jonathan Chang
Assignee: Jonathan Chang
Priority: Minor
Attachments: D147.1.patch, D147.2.patch, D147.3.patch, D147.3.patch
C, Python, etc. all support this magical feature.
--
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-2527) Consecutive string literals should be combined into a single string literal.
[ https://issues.apache.org/jira/browse/HIVE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141689#comment-13141689 ] John Sichi commented on HIVE-2527: -- I'll email it to you. Some of them may be bogus due to side-effects from previous real failures. But there's going to be a huge amount of diff from every existing string literal changing, so it might be better to figure out a way to make the rendering come out the same way as before. Consecutive string literals should be combined into a single string literal. Key: HIVE-2527 URL: https://issues.apache.org/jira/browse/HIVE-2527 Project: Hive Issue Type: Improvement Reporter: Jonathan Chang Assignee: Jonathan Chang Priority: Minor Attachments: D147.1.patch, D147.2.patch, D147.3.patch, D147.3.patch C, Python, etc. all support this magical feature. -- 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-2536) Support scientific notation for Double literals
[ https://issues.apache.org/jira/browse/HIVE-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13140517#comment-13140517 ] John Sichi commented on HIVE-2536: -- +1, will commit when tests pass. Support scientific notation for Double literals --- Key: HIVE-2536 URL: https://issues.apache.org/jira/browse/HIVE-2536 Project: Hive Issue Type: Bug Reporter: Jonathan Chang Assignee: Jonathan Chang Attachments: D129.1.patch, D129.1.patch Of the form 1.0e10. -- 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-2536) Support scientific notation for Double literals
[ https://issues.apache.org/jira/browse/HIVE-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2536. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Committed to trunk. Thanks Jonathan! Support scientific notation for Double literals --- Key: HIVE-2536 URL: https://issues.apache.org/jira/browse/HIVE-2536 Project: Hive Issue Type: Bug Reporter: Jonathan Chang Assignee: Jonathan Chang Fix For: 0.9.0 Attachments: D129.1.patch, D129.1.patch, D129.1.patch Of the form 1.0e10. -- 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-1592) ProxyFileSystem.close calls super.close twice.
[
https://issues.apache.org/jira/browse/HIVE-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi updated HIVE-1592:
-
Resolution: Fixed
Fix Version/s: 0.9.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk. Thanks Ashutosh!
ProxyFileSystem.close calls super.close twice.
--
Key: HIVE-1592
URL: https://issues.apache.org/jira/browse/HIVE-1592
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Affects Versions: 0.7.0, 0.8.0, 0.9.0
Reporter: John Sichi
Assignee: Ashutosh Chauhan
Priority: Minor
Fix For: 0.9.0
Attachments: hive-1592.patch
public void close() throws IOException {
super.close();
super.close();
}
--
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-2533) test load_fs.q failing
[ https://issues.apache.org/jira/browse/HIVE-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138620#comment-13138620 ] John Sichi commented on HIVE-2533: -- This is due to https://issues.apache.org/jira/browse/HDFS-13 load_fs.q references '/tmp/load2_*'. Namit, look in your /tmp directory and you'll find files with names like somehost.facebook.com:9000 One fix is to just delete those files, but something within FB environment creates them there occasionally, so we may want to come up with a better fix. 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] [Commented] (HIVE-2532) Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned.
[ https://issues.apache.org/jira/browse/HIVE-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138628#comment-13138628 ] John Sichi commented on HIVE-2532: -- contrib/src/java/org/apache/hadoop/hive/contrib/udf/UDFRowSequence.java (I used this for the existing stateful test cases.) Evaluation of non-deterministic/stateful UDFs should not be skipped even if constant oi is returned. Key: HIVE-2532 URL: https://issues.apache.org/jira/browse/HIVE-2532 Project: Hive Issue Type: Bug Reporter: Jonathan Chang Assignee: Jonathan Chang Even if constant oi is returned, these may have stateful/side-effect behavior and hence need to be called each cycle. -- 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-2531) Allow people to use only issue numbers without 'HIVE-' prefix with `arc diff --jira`.
[ https://issues.apache.org/jira/browse/HIVE-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2531. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed +1, committed to trunk. Thanks Marek! Allow people to use only issue numbers without 'HIVE-' prefix with `arc diff --jira`. - Key: HIVE-2531 URL: https://issues.apache.org/jira/browse/HIVE-2531 Project: Hive Issue Type: Bug Reporter: Marek Sapota Assignee: Marek Sapota Fix For: 0.9.0 Attachments: D93.1.patch Allow people to use only issue numbers without 'HIVE-' prefix with `arc diff --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] [Updated] (HIVE-2391) published POMs in Maven repo are incorrect
[ https://issues.apache.org/jira/browse/HIVE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2391: - Status: Open (was: Patch Available) published POMs in Maven repo are incorrect -- Key: HIVE-2391 URL: https://issues.apache.org/jira/browse/HIVE-2391 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.7.1 Reporter: Alejandro Abdelnur Assignee: Carl Steinbach Priority: Critical Fix For: 0.8.0 Attachments: HIVE-2391.1.patch.txt, HIVE-2391.2.patch.txt, HIVE-2391.wip.1.patch.txt The Hive artifacts published in Apache Maven SNAPSHOTS repo are incorrect. Dependencies are not complete. Even after adding as dependencies ALL the Hive artifacts it is not possible to compile a project using Hive JARs (I'm trying to integrate Oozie Hive Action using Apache Hive). As a reference the Hive CDH POMs dependencies could be used (Using those artifacts I'm able to compile/test/run Hive from within Oozie). -- 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-1592) ProxyFileSystem.close calls super.close twice.
[
https://issues.apache.org/jira/browse/HIVE-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi reassigned HIVE-1592:
Assignee: Ashutosh Chauhan (was: Joydeep Sen Sarma)
ProxyFileSystem.close calls super.close twice.
--
Key: HIVE-1592
URL: https://issues.apache.org/jira/browse/HIVE-1592
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Affects Versions: 0.7.0, 0.8.0, 0.9.0
Reporter: John Sichi
Assignee: Ashutosh Chauhan
Priority: Minor
Attachments: hive-1592.patch
public void close() throws IOException {
super.close();
super.close();
}
--
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-1592) ProxyFileSystem.close calls super.close twice.
[
https://issues.apache.org/jira/browse/HIVE-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138860#comment-13138860
]
John Sichi commented on HIVE-1592:
--
+1. Will commit when tests pass.
ProxyFileSystem.close calls super.close twice.
--
Key: HIVE-1592
URL: https://issues.apache.org/jira/browse/HIVE-1592
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Affects Versions: 0.7.0, 0.8.0, 0.9.0
Reporter: John Sichi
Assignee: Ashutosh Chauhan
Priority: Minor
Attachments: hive-1592.patch
public void close() throws IOException {
super.close();
super.close();
}
--
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-2486) Phabricator for code review
[ https://issues.apache.org/jira/browse/HIVE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-2486: Assignee: Marek Sapota Phabricator for code review --- Key: HIVE-2486 URL: https://issues.apache.org/jira/browse/HIVE-2486 Project: Hive Issue Type: Bug Reporter: Marek Sapota Assignee: Marek Sapota Attachments: D51.1.patch, D51.2.patch, 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-tabpanelfocusedCommentId=13136583#comment-13136583 ] John Sichi commented on HIVE-2486: -- +1. Will commit. Could you re-attach the lastest patch granting ASF rights? Phabricator for code review --- Key: HIVE-2486 URL: https://issues.apache.org/jira/browse/HIVE-2486 Project: Hive Issue Type: Bug Reporter: Marek Sapota Assignee: Marek Sapota Attachments: D51.1.patch, D51.2.patch, 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] [Resolved] (HIVE-2486) Phabricator for code review
[ https://issues.apache.org/jira/browse/HIVE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2486. -- Resolution: Fixed Fix Version/s: 0.9.0 Hadoop Flags: Reviewed Committed to trunk. Thanks Marek! Phabricator for code review --- Key: HIVE-2486 URL: https://issues.apache.org/jira/browse/HIVE-2486 Project: Hive Issue Type: Bug Reporter: Marek Sapota Assignee: Marek Sapota Fix For: 0.9.0 Attachments: D51.1.patch, D51.2.patch, D51.2.patch, 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-tabpanelfocusedCommentId=13136590#comment-13136590 ] John Sichi commented on HIVE-2486: -- (I also committed an svn:ignore propset with the latest contents of .gitignore; it was slightly out of date.) Phabricator for code review --- Key: HIVE-2486 URL: https://issues.apache.org/jira/browse/HIVE-2486 Project: Hive Issue Type: Bug Reporter: Marek Sapota Assignee: Marek Sapota Fix For: 0.9.0 Attachments: D51.1.patch, D51.2.patch, D51.2.patch, 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] [Resolved] (HIVE-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi resolved HIVE-2509. -- Resolution: Fixed Fix Version/s: 0.9.0 Release Note: This change adds parser support for typed integer literal variants (tinyint, smallint, and bigint). Hadoop Flags: Reviewed Committed to trunk. Thanks Jonathan! Can you update the wiki with the new syntax? 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 Fix For: 0.9.0 Attachments: D15.1.patch, D15.1.patch, D15.2.patch, D15.2.patch, D15.3.patch, D15.3.patch, D15.4.patch, D15.4.patch, D15.4.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-2501) When new instance of Hive (class) is created, the current database is reset to default (current database shouldn't be changed).
[ https://issues.apache.org/jira/browse/HIVE-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13135352#comment-13135352 ] John Sichi commented on HIVE-2501: -- +1. Will commit when tests pass. When new instance of Hive (class) is created, the current database is reset to default (current database shouldn't be changed). --- Key: HIVE-2501 URL: https://issues.apache.org/jira/browse/HIVE-2501 Project: Hive Issue Type: Bug Reporter: Robert Surówka Assignee: Robert Surówka Priority: Minor Attachments: HIVE-2501.1.patch, HIVE-2501.2.patch This bug manifested to me, when first thing I did after starting Hive, was to call use db_name; but then calling show tables; was still showing tables from the default database (and I had to call use again to actually change database). This bug might have manifested only due to a specific Hive deployment I am using (I didn't investigate this issue that deeply). -- 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-tabpanelfocusedCommentId=13135411#comment-13135411 ] John Sichi commented on HIVE-2509: -- Try now...I just granted you write access. 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 Fix For: 0.9.0 Attachments: D15.1.patch, D15.1.patch, D15.2.patch, D15.2.patch, D15.3.patch, D15.3.patch, D15.4.patch, D15.4.patch, D15.4.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-2521) Update wiki links in README file
[ https://issues.apache.org/jira/browse/HIVE-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2521: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) +1, committed to 0.8 and trunk. Thanks Carl! Update wiki links in README file Key: HIVE-2521 URL: https://issues.apache.org/jira/browse/HIVE-2521 Project: Hive Issue Type: Task Reporter: Carl Steinbach Assignee: Carl Steinbach Priority: Blocker Fix For: 0.8.0 Attachments: HIVE-2521.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-2509) Literal bigint
[ https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13134435#comment-13134435 ] John Sichi commented on HIVE-2509: -- Patch is not applying cleanly on latest trunk...can you rebase? 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, D15.2.patch, D15.2.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] [Assigned] (HIVE-727) Hive Server getSchema() returns wrong schema for Explain queries
[ https://issues.apache.org/jira/browse/HIVE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-727: --- Assignee: Eric Hwang Hive Server getSchema() returns wrong schema for Explain queries -- Key: HIVE-727 URL: https://issues.apache.org/jira/browse/HIVE-727 Project: Hive Issue Type: Bug Reporter: Eric Hwang Assignee: Eric Hwang Attachments: Hive-727.patch The Hive Server's getSchema() function will return a schema with zero fields when executing an Explain... query. A quick fix might be to set the default schema to be exactly one column 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] [Assigned] (HIVE-727) Hive Server getSchema() returns wrong schema for Explain queries
[ https://issues.apache.org/jira/browse/HIVE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-727: --- Assignee: Prasad Mujumdar (was: Eric Hwang) Hive Server getSchema() returns wrong schema for Explain queries -- Key: HIVE-727 URL: https://issues.apache.org/jira/browse/HIVE-727 Project: Hive Issue Type: Bug Reporter: Eric Hwang Assignee: Prasad Mujumdar Attachments: Hive-727.patch The Hive Server's getSchema() function will return a schema with zero fields when executing an Explain... query. A quick fix might be to set the default schema to be exactly one column 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] [Updated] (HIVE-2501) When new instance of Hive (class) is created, the current database is reset to default (current database shouldn't be changed).
[ https://issues.apache.org/jira/browse/HIVE-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi updated HIVE-2501: - Status: Open (was: Patch Available) When new instance of Hive (class) is created, the current database is reset to default (current database shouldn't be changed). --- Key: HIVE-2501 URL: https://issues.apache.org/jira/browse/HIVE-2501 Project: Hive Issue Type: Bug Reporter: Robert Surówka Assignee: Robert Surówka Priority: Minor Attachments: HIVE-2501.1.patch This bug manifested to me, when first thing I did after starting Hive, was to call use db_name; but then calling show tables; was still showing tables from the default database (and I had to call use again to actually change database). This bug might have manifested only due to a specific Hive deployment I am using (I didn't investigate this issue that deeply). -- 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-tabpanelfocusedCommentId=13134487#comment-13134487
]
John Sichi commented on HIVE-2509:
--
It's still not applying. The reason is that for
PrimitiveObjectInspectorFactory.java, the latest svn already has
{noformat}
import org.apache.hadoop.hive.serde2.io.ByteWritable;
{noformat}
but your patches have
{noformat}
-import org.apache.hadoop.io.ByteWritable;
+import org.apache.hadoop.hive.serde2.io.ByteWritable;
{noformat}
Maybe your git tree is stale?
Note that phabricator just works off of your diff (with a huge diff context
flag setting); according to Marek, it's not currently doing anything with
what's actually in the repo.
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, D15.2.patch, D15.2.patch,
D15.3.patch, D15.3.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-tabpanelfocusedCommentId=13134512#comment-13134512 ] John Sichi commented on HIVE-2509: -- Note that the conflict came from your HIVE-1360 patch. 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, D15.2.patch, D15.2.patch, D15.3.patch, D15.3.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-tabpanelfocusedCommentId=13134554#comment-13134554 ] John Sichi commented on HIVE-2509: -- +1, will commit when tests pass. A good followup would be negative tests for out of range constants. 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, D15.2.patch, D15.2.patch, D15.3.patch, D15.3.patch, D15.4.patch, D15.4.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-2501) When new instance of Hive (class) is created, the current database is reset to default (current database shouldn't be changed).
[ https://issues.apache.org/jira/browse/HIVE-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13134650#comment-13134650 ] John Sichi commented on HIVE-2501: -- We don't want to create+drop the test database for every .q file. Instead of creating a new .q file, I think you can add a Java-level testcase to ql/src/test/org/apache/hadoop/hive/ql/metadata/TestHive.java When new instance of Hive (class) is created, the current database is reset to default (current database shouldn't be changed). --- Key: HIVE-2501 URL: https://issues.apache.org/jira/browse/HIVE-2501 Project: Hive Issue Type: Bug Reporter: Robert Surówka Assignee: Robert Surówka Priority: Minor Attachments: HIVE-2501.1.patch This bug manifested to me, when first thing I did after starting Hive, was to call use db_name; but then calling show tables; was still showing tables from the default database (and I had to call use again to actually change database). This bug might have manifested only due to a specific Hive deployment I am using (I didn't investigate this issue that deeply). -- 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-2523) add a new builtins subproject
[ https://issues.apache.org/jira/browse/HIVE-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sichi reassigned HIVE-2523: Assignee: John Sichi add a new builtins subproject - Key: HIVE-2523 URL: https://issues.apache.org/jira/browse/HIVE-2523 Project: Hive Issue Type: Improvement Components: UDF Reporter: John Sichi Assignee: John Sichi Fix For: 0.9.0 Now that we have a PDK, we can make it easier to add builtin functions to Hive by putting them in a plugin which automatically gets loaded by Hive. This issue will add the necessary framework and one example function; then new functions can be added here, and over time we could migrate old ones here if desired. -- 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-2524) enhance PDK with validation and utility functions
enhance PDK with validation and utility functions - Key: HIVE-2524 URL: https://issues.apache.org/jira/browse/HIVE-2524 Project: Hive Issue Type: Improvement Components: UDF Reporter: John Sichi Assignee: Marek Sapota Fix For: 0.9.0 Writing a robust UDF implementation requires a lot of boilerplate code such as argument type checking. We should add utility libraries to make UDF's easier to write. -- 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
