[jira] [Commented] (HIVE-3265) HiveHistory.printRowCount() throws NPE
[ https://issues.apache.org/jira/browse/HIVE-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442310#comment-13442310 ] Carl Steinbach commented on HIVE-3265: -- +1. Will commit if tests pass. HiveHistory.printRowCount() throws NPE -- Key: HIVE-3265 URL: https://issues.apache.org/jira/browse/HIVE-3265 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.8.1 Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: HIVE-3265.1.patch.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3408) A race condition is caused within QueryPlan class
Muga Nishizawa created HIVE-3408:
Summary: A race condition is caused within QueryPlan class
Key: HIVE-3408
URL: https://issues.apache.org/jira/browse/HIVE-3408
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.7.1
Environment: * Java 1.6.0_21, Java HotSpot(TM) 64-Bit Server VM
* Ubuntu 10.04
Reporter: Muga Nishizawa
Hive's threads are stopped at HashMap.getEntry(..) that is used within
QueryPlan#extractCounters() and QueryPlan#updateCountersInQueryPlan(). It
seems that a race condition problem of a HashSet object is caused when
extractCounters() and updateCountersInQueryPlan() are concurrently executed. I
hit the problem with Hive 0.7.1 but, I think that it also is caused with 0.8.1.
The following is a part of the thread dump.
{quote}
Thread-1091 prio=10 tid=0x7fd17112b000 nid=0x1100 runnable
[0x7fd175f6]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at org.apache.hadoop.hive.ql.QueryPlan.extractCounters(QueryPlan.java:342)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:419)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
Thread-1090 prio=10 tid=0x7fd17012f000 nid=0x10ff runnable
[0x7fd175152000]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at
org.apache.hadoop.hive.ql.QueryPlan.updateCountersInQueryPlan(QueryPlan.java:297)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:420)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3408) A race condition is caused within QueryPlan class
[
https://issues.apache.org/jira/browse/HIVE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Muga Nishizawa updated HIVE-3408:
-
Attachment: race-condition-of-done-field.patch
To solve the problem, I attached a patch on this ticket. Please check it.
A race condition is caused within QueryPlan class
-
Key: HIVE-3408
URL: https://issues.apache.org/jira/browse/HIVE-3408
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.7.1
Environment: * Java 1.6.0_21, Java HotSpot(TM) 64-Bit Server VM
* Ubuntu 10.04
Reporter: Muga Nishizawa
Attachments: race-condition-of-done-field.patch
Hive's threads are stopped at HashMap.getEntry(..) that is used within
QueryPlan#extractCounters() and QueryPlan#updateCountersInQueryPlan(). It
seems that a race condition problem of a HashSet object is caused when
extractCounters() and updateCountersInQueryPlan() are concurrently executed.
I hit the problem with Hive 0.7.1 but, I think that it also is caused with
0.8.1.
The following is a part of the thread dump.
{quote}
Thread-1091 prio=10 tid=0x7fd17112b000 nid=0x1100 runnable
[0x7fd175f6]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at org.apache.hadoop.hive.ql.QueryPlan.extractCounters(QueryPlan.java:342)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:419)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
Thread-1090 prio=10 tid=0x7fd17012f000 nid=0x10ff runnable
[0x7fd175152000]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at
org.apache.hadoop.hive.ql.QueryPlan.updateCountersInQueryPlan(QueryPlan.java:297)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:420)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3408) A race condition is caused within QueryPlan class
[
https://issues.apache.org/jira/browse/HIVE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Steinbach updated HIVE-3408:
-
Labels: Concurrency (was: )
A race condition is caused within QueryPlan class
-
Key: HIVE-3408
URL: https://issues.apache.org/jira/browse/HIVE-3408
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.7.1
Environment: * Java 1.6.0_21, Java HotSpot(TM) 64-Bit Server VM
* Ubuntu 10.04
Reporter: Muga Nishizawa
Labels: Concurrency
Attachments: race-condition-of-done-field.patch
Hive's threads are stopped at HashMap.getEntry(..) that is used within
QueryPlan#extractCounters() and QueryPlan#updateCountersInQueryPlan(). It
seems that a race condition problem of a HashSet object is caused when
extractCounters() and updateCountersInQueryPlan() are concurrently executed.
I hit the problem with Hive 0.7.1 but, I think that it also is caused with
0.8.1.
The following is a part of the thread dump.
{quote}
Thread-1091 prio=10 tid=0x7fd17112b000 nid=0x1100 runnable
[0x7fd175f6]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at org.apache.hadoop.hive.ql.QueryPlan.extractCounters(QueryPlan.java:342)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:419)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
Thread-1090 prio=10 tid=0x7fd17012f000 nid=0x10ff runnable
[0x7fd175152000]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at
org.apache.hadoop.hive.ql.QueryPlan.updateCountersInQueryPlan(QueryPlan.java:297)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:420)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3408) A race condition is caused within QueryPlan class
[
https://issues.apache.org/jira/browse/HIVE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Muga Nishizawa updated HIVE-3408:
-
Description:
Hive's threads are stopped at HashMap.getEntry(..) that is used within
QueryPlan#extractCounters() and QueryPlan#updateCountersInQueryPlan(). It
seems that a race condition problem of a HashSet object is caused when
extractCounters() and updateCountersInQueryPlan() are concurrently executed. I
hit the problem with Hive 0.7.1 but, I think that it also is caused with 0.8.1.
The problem is reported by several persons on mailing list.
http://mail-archives.apache.org/mod_mbox/hive-dev/201201.mbox/%3CCAKTRiE+3x31FDy+3F0c+jZSXQrhxBgT4DOyfZddm7sdX+cu=z...@mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/hive-user/201202.mbox/%3cfc28ccd9-9c75-4f8d-b272-3d50f663a...@gmail.com%3E
The following is a part of my thread dump.
{quote}
Thread-1091 prio=10 tid=0x7fd17112b000 nid=0x1100 runnable
[0x7fd175f6]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at org.apache.hadoop.hive.ql.QueryPlan.extractCounters(QueryPlan.java:342)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:419)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
Thread-1090 prio=10 tid=0x7fd17012f000 nid=0x10ff runnable
[0x7fd175152000]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at
org.apache.hadoop.hive.ql.QueryPlan.updateCountersInQueryPlan(QueryPlan.java:297)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:420)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
{quote}
was:
Hive's threads are stopped at HashMap.getEntry(..) that is used within
QueryPlan#extractCounters() and QueryPlan#updateCountersInQueryPlan(). It
seems that a race condition problem of a HashSet object is caused when
extractCounters() and updateCountersInQueryPlan() are concurrently executed. I
hit the problem with Hive 0.7.1 but, I think that it also is caused with 0.8.1.
The following is a part of the thread dump.
{quote}
Thread-1091 prio=10 tid=0x7fd17112b000 nid=0x1100 runnable
[0x7fd175f6]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at org.apache.hadoop.hive.ql.QueryPlan.extractCounters(QueryPlan.java:342)
at org.apache.hadoop.hive.ql.QueryPlan.getQueryPlan(QueryPlan.java:419)
at org.apache.hadoop.hive.ql.QueryPlan.toString(QueryPlan.java:592)
at
org.apache.hadoop.hive.ql.history.HiveHistory.logPlanProgress(HiveHistory.java:493)
at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:395)
at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:686)
at org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:123)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)
Thread-1090 prio=10 tid=0x7fd17012f000 nid=0x10ff runnable
[0x7fd175152000]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:347)
at java.util.HashMap.containsKey(HashMap.java:335)
at java.util.HashSet.contains(HashSet.java:184)
at
org.apache.hadoop.hive.ql.QueryPlan.updateCountersInQueryPlan(QueryPlan.java:297)
at
[jira] [Created] (HIVE-3409) Increase test.timeout value
Carl Steinbach created HIVE-3409: Summary: Increase test.timeout value Key: HIVE-3409 URL: https://issues.apache.org/jira/browse/HIVE-3409 Project: Hive Issue Type: Bug Components: Testing Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3409) Increase test.timeout value
[ https://issues.apache.org/jira/browse/HIVE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442344#comment-13442344 ] Carl Steinbach commented on HIVE-3409: -- It looks like the builds are failing because TestCliDriver is timing out after exceeding the timeout value defined by test.timeout=1820ms (303 minutes). I doubled the value in the Jenkins job configuration and this seems to have fixed the problem. Failed job: https://builds.apache.org/job/Hive-trunk-h0.21/1630/ Success after doubling test.timeout value: https://builds.apache.org/job/Hive-trunk-h0.21/1632/ Increase test.timeout value --- Key: HIVE-3409 URL: https://issues.apache.org/jira/browse/HIVE-3409 Project: Hive Issue Type: Bug Components: Testing Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3409) Increase test.timeout value
[ https://issues.apache.org/jira/browse/HIVE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3409: - Attachment: HIVE-3409.1.patch.txt Increase test.timeout value --- Key: HIVE-3409 URL: https://issues.apache.org/jira/browse/HIVE-3409 Project: Hive Issue Type: Bug Components: Testing Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-3409.1.patch.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Review Request: HIVE-3409. Increase test.timeout value
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6780/ --- Review request for hive and Ashutosh Chauhan. Description --- commit bfb69f3cb607a2daadcff07dd87b8924ae19ae2b Author: Carl Steinbach c...@cloudera.com Date: Mon Aug 27 03:05:19 2012 -0700 Add test.junit.timeout to build.properties, and double value build-common.xml | 3 +-- build.properties | 6 ++ common/build.xml | 2 +- 3 files changed, 8 insertions(+), 3 deletions(-) This addresses bug HIVE-3409. https://issues.apache.org/jira/browse/HIVE-3409 Diffs - build-common.xml f2697e1 build.properties ff9eba9 common/build.xml 2712c03 Diff: https://reviews.apache.org/r/6780/diff/ Testing --- Thanks, Carl Steinbach
Re: Hive-trunk-h0.21 - Build # 1630 - Still Failing
I submitted a patch for this bug here: https://issues.apache.org/jira/browse/HIVE-3409 On Sun, Aug 26, 2012 at 12:40 PM, Carl Steinbach c...@cloudera.com wrote: It looks like the builds are failing because TestCliDriver is timing out after exceeding the timeout value defined by test.timeout=1820ms (303 minutes). I doubled the value in the Jenkins job configuration. If this fixes the problem we should probably update the value in build-common.xml. Thanks. Carl On Sun, Aug 26, 2012 at 6:28 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: Changes for Build #1627 [namit] HIVE-3072 Hive List Bucketing - DDL support (Gang Tim Liu via namit) [kevinwilfong] HIVE-3396. hive.stats.reliable config causes FileSinkOperator to fail when writing empty file. (kevinwilfong reviewed by njain) Changes for Build #1628 [namit] HIVE-3406 Yet better error message in CLI on invalid column name (Navis via namit) Changes for Build #1629 [cws] HIVE-3345. Add junit exclude utility to disable testcases (Zhenxiao Luo via cws) Changes for Build #1630 [cws] HIVE-3365. Upgrade Hive's Avro dependency to version 1.7 (Shreepadma Venugopalan via cws) 2 tests failed. FAILED: org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_udf_not Error Message: Timeout occurred. Please note the time in the report does not reflect the time until the timeout. Stack Trace: junit.framework.AssertionFailedError: Timeout occurred. Please note the time in the report does not reflect the time until the timeout. at net.sf.antcontrib.logic.ForTask.doSequentialIteration(ForTask.java:259) at net.sf.antcontrib.logic.ForTask.doToken(ForTask.java:268) at net.sf.antcontrib.logic.ForTask.doTheTasks(ForTask.java:324) at net.sf.antcontrib.logic.ForTask.execute(ForTask.java:244) FAILED: org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1 Error Message: Unexpected exception See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. Stack Trace: junit.framework.AssertionFailedError: Unexpected exception See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. at junit.framework.Assert.fail(Assert.java:47) at org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1(TestNegativeCliDriver.java:11278) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906) The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1630) Status: Still Failing Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1630/ to view the results.
[jira] [Updated] (HIVE-3409) Increase test.timeout value
[ https://issues.apache.org/jira/browse/HIVE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3409: - Status: Patch Available (was: Open) Review request: https://reviews.apache.org/r/6780/ Increase test.timeout value --- Key: HIVE-3409 URL: https://issues.apache.org/jira/browse/HIVE-3409 Project: Hive Issue Type: Bug Components: Testing Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-3409.1.patch.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Need help urgently....
Can i load data from MVS to hadoop/hive by using sqoop.If yes please help me with the steps and if no, please suggest me some other alternatives. Need Urgent help. Thanks in Advance. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
[jira] [Commented] (HIVE-3171) Bucketed sort merge join doesn't work when multiple files exist for small alias
[
https://issues.apache.org/jira/browse/HIVE-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442354#comment-13442354
]
Carl Steinbach commented on HIVE-3171:
--
@Namit: The Apache Hive Project Bylaws are located here:
https://cwiki.apache.org/confluence/display/Hive/Bylaws
The bylaws explicitly prohibit committers from voting on their own patches, but
they don't prohibit committers from committing their own patches as long as
another committer has already reviewed and +1'd the patch. It's also worth
noting that the bylaws stipulate that the +1 vote must be sent to dev@hive, and
that 24 hours must elapse between the first +1 vote and the point at which the
patch is committed.
Bucketed sort merge join doesn't work when multiple files exist for small
alias
---
Key: HIVE-3171
URL: https://issues.apache.org/jira/browse/HIVE-3171
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.10.0
Reporter: Joey Echeverria
Assignee: Navis
Labels: bucketing, joins, partitioning
Attachments: HIVE-3171.1.patch.txt
Executing a query with the MAPJOIN hint and the bucketed sort merge join
optimizations enabled:
{noformat}
set hive.input.format=org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat;
set hive.optimize.bucketmapjoin = true;
set hive.optimize.bucketmapjoin.sortedmerge = true;
{noformat}
works fine with partitioned tables if there is only one partition in the
table. However, if you add a second partition, Hive attempts to do a regular
map-side join which can fail because the tables are too large. Hive ought to
be able to still do the bucketed sort merge join with partitions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Need help urgently....
Hi Ashok, You're more likely to get an answer if you email one of the Sqoop mailing lists: http://sqoop.apache.org/mail-lists.html Thanks. Carl On Mon, Aug 27, 2012 at 3:09 AM, ashok.sa...@wipro.com wrote: Can i load data from MVS to hadoop/hive by using sqoop.If yes please help me with the steps and if no, please suggest me some other alternatives. Need Urgent help. Thanks in Advance. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Need help urgently....
Hi Ashok, Not sure what is MVS, but considering it some sort of database, as long as ports are open/ACL's are established, using sqoop to have data on hdfs is easy as a command - sqoop import -D mapred.job.queue.name=your-queue-name --connect jdbc:oracle:thin:@//your-db:1521/your-db-sid --username your-username --table your-table --target-dir your-hdfs-dir --password your-pwd -m 1 Thanks Rekha On 27/08/12 3:39 PM, ashok.sa...@wipro.com ashok.sa...@wipro.com wrote: Can i load data from MVS to hadoop/hive by using sqoop.If yes please help me with the steps and if no, please suggest me some other alternatives. Need Urgent help. Thanks in Advance. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
[jira] [Commented] (HIVE-3086) Skewed Join Optimization
[ https://issues.apache.org/jira/browse/HIVE-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442372#comment-13442372 ] Carl Steinbach commented on HIVE-3086: -- @Namit: Is this a work in progress? Skewed Join Optimization Key: HIVE-3086 URL: https://issues.apache.org/jira/browse/HIVE-3086 Project: Hive Issue Type: New Feature Reporter: Nadeem Moidu Assignee: Namit Jain During a join operation, if one of the columns has a skewed key, it can cause that particular reducer to become the bottleneck. The following feature will address it: https://cwiki.apache.org/confluence/display/Hive/Skewed+Join+Optimization -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Review Request: HIVE-3409. Increase test.timeout value
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6780/#review10775 --- Ship it! Ship It! - Ashutosh Chauhan On Aug. 27, 2012, 10:09 a.m., Carl Steinbach wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6780/ --- (Updated Aug. 27, 2012, 10:09 a.m.) Review request for hive and Ashutosh Chauhan. Description --- commit bfb69f3cb607a2daadcff07dd87b8924ae19ae2b Author: Carl Steinbach c...@cloudera.com Date: Mon Aug 27 03:05:19 2012 -0700 Add test.junit.timeout to build.properties, and double value build-common.xml | 3 +-- build.properties | 6 ++ common/build.xml | 2 +- 3 files changed, 8 insertions(+), 3 deletions(-) This addresses bug HIVE-3409. https://issues.apache.org/jira/browse/HIVE-3409 Diffs - build-common.xml f2697e1 build.properties ff9eba9 common/build.xml 2712c03 Diff: https://reviews.apache.org/r/6780/diff/ Testing --- Thanks, Carl Steinbach
Re: Review Request: HIVE-3409. Increase test.timeout value
On Aug. 27, 2012, 3:07 p.m., Ashutosh Chauhan wrote: Ship It! +1 Please commit. - Ashutosh --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6780/#review10775 --- On Aug. 27, 2012, 10:09 a.m., Carl Steinbach wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6780/ --- (Updated Aug. 27, 2012, 10:09 a.m.) Review request for hive and Ashutosh Chauhan. Description --- commit bfb69f3cb607a2daadcff07dd87b8924ae19ae2b Author: Carl Steinbach c...@cloudera.com Date: Mon Aug 27 03:05:19 2012 -0700 Add test.junit.timeout to build.properties, and double value build-common.xml | 3 +-- build.properties | 6 ++ common/build.xml | 2 +- 3 files changed, 8 insertions(+), 3 deletions(-) This addresses bug HIVE-3409. https://issues.apache.org/jira/browse/HIVE-3409 Diffs - build-common.xml f2697e1 build.properties ff9eba9 common/build.xml 2712c03 Diff: https://reviews.apache.org/r/6780/diff/ Testing --- Thanks, Carl Steinbach
Build failed in Jenkins: Hive-0.9.1-SNAPSHOT-h0.21 #118
See https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/ -- [...truncated 5429 lines...] [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/jdbc/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/jdbc/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/ws/hive/jdbc/src/test/resources does not exist. init: [echo] Project: jdbc create-dirs: [echo] Project: hwi [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hwi [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hwi/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hwi/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hwi/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hwi/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hwi/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/ws/hive/hwi/src/test/resources does not exist. init: [echo] Project: hwi create-dirs: [echo] Project: hbase-handler [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hbase-handler [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hbase-handler/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hbase-handler/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hbase-handler/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hbase-handler/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/hbase-handler/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/ws/hive/hbase-handler/src/test/resources does not exist. init: [echo] Project: hbase-handler create-dirs: [echo] Project: pdk [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/pdk [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/pdk/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/pdk/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/pdk/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/pdk/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/pdk/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/ws/hive/pdk/src/test/resources does not exist. init: [echo] Project: pdk create-dirs: [echo] Project: builtins [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/builtins [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/builtins/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/builtins/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/builtins/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/builtins/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/118/artifact/hive/build/builtins/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/ws/hive/builtins/src/test/resources does not exist. init: [echo] Project: builtins jar: [echo] Project: hive create-dirs: [echo] Project: shims [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/ws/hive/shims/src/test/resources does not exist. init: [echo] Project: shims ivy-init-settings: [echo] Project: shims ivy-resolve: [echo] Project: shims [ivy:resolve] :: loading settings :: file = https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21/ws/hive/ivy/ivysettings.xml [ivy:resolve] downloading http://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.3/zookeeper-3.4.3.jar ... [ivy:resolve]
Build failed in Jenkins: Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false #118
See https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/118/ -- [...truncated 5572 lines...] [ivy:resolve] .. (273kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] commons-httpclient#commons-httpclient;3.0.1!commons-httpclient.jar (58ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/commons-codec/commons-codec/1.3/commons-codec-1.3.jar ... [ivy:resolve] ... (45kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] commons-codec#commons-codec;1.3!commons-codec.jar (34ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/commons-net/commons-net/1.4.1/commons-net-1.4.1.jar ... [ivy:resolve] .. (176kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] commons-net#commons-net;1.4.1!commons-net.jar (27ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/mortbay/jetty/jetty/6.1.14/jetty-6.1.14.jar ... [ivy:resolve] (504kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.mortbay.jetty#jetty;6.1.14!jetty.jar (54ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-util/6.1.14/jetty-util-6.1.14.jar ... [ivy:resolve] ... (159kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.mortbay.jetty#jetty-util;6.1.14!jetty-util.jar (41ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/tomcat/jasper-runtime/5.5.12/jasper-runtime-5.5.12.jar ... [ivy:resolve] .. (74kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] tomcat#jasper-runtime;5.5.12!jasper-runtime.jar (31ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/tomcat/jasper-compiler/5.5.12/jasper-compiler-5.5.12.jar ... [ivy:resolve] (395kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] tomcat#jasper-compiler;5.5.12!jasper-compiler.jar (24ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-api-2.1/6.1.14/jsp-api-2.1-6.1.14.jar ... [ivy:resolve] ... (131kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.mortbay.jetty#jsp-api-2.1;6.1.14!jsp-api-2.1.jar (150ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-2.1/6.1.14/jsp-2.1-6.1.14.jar ... [ivy:resolve] .. (1000kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.mortbay.jetty#jsp-2.1;6.1.14!jsp-2.1.jar (156ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/commons-el/commons-el/1.0/commons-el-1.0.jar ... [ivy:resolve] .. (109kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] commons-el#commons-el;1.0!commons-el.jar (49ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/net/java/dev/jets3t/jets3t/0.7.1/jets3t-0.7.1.jar ... [ivy:resolve] .. (368kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] net.java.dev.jets3t#jets3t;0.7.1!jets3t.jar (78ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/mortbay/jetty/servlet-api-2.5/6.1.14/servlet-api-2.5-6.1.14.jar ... [ivy:resolve] ... (129kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.mortbay.jetty#servlet-api-2.5;6.1.14!servlet-api-2.5.jar (32ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/net/sf/kosmosfs/kfs/0.3/kfs-0.3.jar ... [ivy:resolve] ... (11kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] net.sf.kosmosfs#kfs;0.3!kfs.jar (62ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/junit/junit/4.5/junit-4.5.jar ... [ivy:resolve] . (194kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] junit#junit;4.5!junit.jar (33ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/hsqldb/hsqldb/1.8.0.10/hsqldb-1.8.0.10.jar ... [ivy:resolve] (690kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] hsqldb#hsqldb;1.8.0.10!hsqldb.jar (36ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/oro/oro/2.0.8/oro-2.0.8.jar ... [ivy:resolve] . (63kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] oro#oro;2.0.8!oro.jar (14ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/eclipse/jdt/core/3.1.1/core-3.1.1.jar ... [ivy:resolve]
[jira] [Commented] (HIVE-3086) Skewed Join Optimization
[ https://issues.apache.org/jira/browse/HIVE-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442512#comment-13442512 ] Namit Jain commented on HIVE-3086: -- yes Skewed Join Optimization Key: HIVE-3086 URL: https://issues.apache.org/jira/browse/HIVE-3086 Project: Hive Issue Type: New Feature Reporter: Nadeem Moidu Assignee: Namit Jain During a join operation, if one of the columns has a skewed key, it can cause that particular reducer to become the bottleneck. The following feature will address it: https://cwiki.apache.org/confluence/display/Hive/Skewed+Join+Optimization -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3171) Bucketed sort merge join doesn't work when multiple files exist for small alias
[
https://issues.apache.org/jira/browse/HIVE-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442517#comment-13442517
]
Namit Jain commented on HIVE-3171:
--
I know the policy, but in most of the cases, I think we don't commit our own
patches.
Anyway, it is not a big deal - I don't feel very comfortable about it, but have
no
reservations if you want to take that path.
Bucketed sort merge join doesn't work when multiple files exist for small
alias
---
Key: HIVE-3171
URL: https://issues.apache.org/jira/browse/HIVE-3171
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.10.0
Reporter: Joey Echeverria
Assignee: Navis
Labels: bucketing, joins, partitioning
Attachments: HIVE-3171.1.patch.txt
Executing a query with the MAPJOIN hint and the bucketed sort merge join
optimizations enabled:
{noformat}
set hive.input.format=org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat;
set hive.optimize.bucketmapjoin = true;
set hive.optimize.bucketmapjoin.sortedmerge = true;
{noformat}
works fine with partitioned tables if there is only one partition in the
table. However, if you add a second partition, Hive attempts to do a regular
map-side join which can fail because the tables are too large. Hive ought to
be able to still do the bucketed sort merge join with partitions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3410) All operators's conf should inherit from a common class
Namit Jain created HIVE-3410: Summary: All operators's conf should inherit from a common class Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3171) Bucketed sort merge join doesn't work when multiple files exist for small alias
[
https://issues.apache.org/jira/browse/HIVE-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Namit Jain updated HIVE-3171:
-
Comment: was deleted
(was: I know the policy, but in most of the cases, I think we don't commit our
own patches.
Anyway, it is not a big deal - I don't feel very comfortable about it, but have
no
reservations if you want to take that path.)
Bucketed sort merge join doesn't work when multiple files exist for small
alias
---
Key: HIVE-3171
URL: https://issues.apache.org/jira/browse/HIVE-3171
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.10.0
Reporter: Joey Echeverria
Assignee: Navis
Labels: bucketing, joins, partitioning
Attachments: HIVE-3171.1.patch.txt
Executing a query with the MAPJOIN hint and the bucketed sort merge join
optimizations enabled:
{noformat}
set hive.input.format=org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat;
set hive.optimize.bucketmapjoin = true;
set hive.optimize.bucketmapjoin.sortedmerge = true;
{noformat}
works fine with partitioned tables if there is only one partition in the
table. However, if you add a second partition, Hive attempts to do a regular
map-side join which can fail because the tables are too large. Hive ought to
be able to still do the bucketed sort merge join with partitions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442566#comment-13442566 ] Namit Jain commented on HIVE-3410: -- https://reviews.facebook.net/D4905 All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3410: - Attachment: hive.3410.1.patch All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Attachments: hive.3410.1.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3410: - Status: Patch Available (was: Open) All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Attachments: hive.3410.1.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-3410: Assignee: Namit Jain All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3410.1.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3410: - Status: Open (was: Patch Available) This patch causes compilation failures in TestOperators and TestPlan. All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3410.1.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Dabrowski updated HIVE-3391: -- Status: Patch Available (was: Open) Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Original Estimate: 72h Remaining Estimate: 72h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Dabrowski updated HIVE-3391: -- Status: Open (was: Patch Available) Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Original Estimate: 72h Remaining Estimate: 72h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Dabrowski updated HIVE-3391: -- Attachment: HIVE-3391.1.patch.txt Please, review my code. Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Attachments: HIVE-3391.1.patch.txt Original Estimate: 72h Remaining Estimate: 72h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Dabrowski updated HIVE-3391: -- Status: Patch Available (was: Open) Simple change. I added another field in HiveDriverRunHookContextImpl, which is command - the original command that Hive is about to execute. No other changes have been made. Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Attachments: HIVE-3391.1.patch.txt Original Estimate: 72h Remaining Estimate: 72h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work logged] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[
https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Dawid Dabrowski logged work on HIVE-3391:
-
Author: Dawid Dabrowski
Created on: 27/Aug/12 21:03
Start Date: 20/Aug/12 21:02
Worklog Time Spent: 96h
Issue Time Tracking
---
Worklog Id: (was: 14035)
Time Spent: 96h
Remaining Estimate: 0h (was: 72h)
Keep the original query in HiveDriverRunHookContextImpl
---
Key: HIVE-3391
URL: https://issues.apache.org/jira/browse/HIVE-3391
Project: Hive
Issue Type: Improvement
Reporter: Dawid Dabrowski
Assignee: Dawid Dabrowski
Priority: Minor
Attachments: HIVE-3391.1.patch.txt
Original Estimate: 72h
Time Spent: 96h
Remaining Estimate: 0h
It'd be useful to have access to the original query in hooks. The hook that's
executed first is HiveDriverRunHook, let's add it there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442685#comment-13442685 ] Kevin Wilfong commented on HIVE-3391: - Could you add a testcase, e.g. write a driver run hook that prints the command to stdout, and add a simple unit test which consists of a query using that hook https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToContribute-AddaUnitTest It'll help prevent anyone from accidentally breaking this change. Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Attachments: HIVE-3391.1.patch.txt Original Estimate: 72h Time Spent: 96h Remaining Estimate: 0h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3391: - Status: Open (was: Patch Available) @Dawid: Please submit a review request on phabricator or reviews.apache.org Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Attachments: HIVE-3391.1.patch.txt Original Estimate: 72h Time Spent: 96h Remaining Estimate: 0h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442733#comment-13442733 ] Carl Steinbach commented on HIVE-3410: -- More comments on phabricator. Thanks. All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3410.1.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Dabrowski updated HIVE-3391: -- Status: Patch Available (was: Open) Patch is available on phabricator Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Attachments: HIVE-3391.1.patch.txt Original Estimate: 72h Time Spent: 96h Remaining Estimate: 0h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442766#comment-13442766 ] Carl Steinbach commented on HIVE-3391: -- Great. Can you please provide a link? Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Attachments: HIVE-3391.1.patch.txt Original Estimate: 72h Time Spent: 96h Remaining Estimate: 0h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3391) Keep the original query in HiveDriverRunHookContextImpl
[ https://issues.apache.org/jira/browse/HIVE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442769#comment-13442769 ] Dawid Dabrowski commented on HIVE-3391: --- https://reviews.facebook.net/D4923 Keep the original query in HiveDriverRunHookContextImpl --- Key: HIVE-3391 URL: https://issues.apache.org/jira/browse/HIVE-3391 Project: Hive Issue Type: Improvement Reporter: Dawid Dabrowski Assignee: Dawid Dabrowski Priority: Minor Attachments: HIVE-3391.1.patch.txt Original Estimate: 72h Time Spent: 96h Remaining Estimate: 0h It'd be useful to have access to the original query in hooks. The hook that's executed first is HiveDriverRunHook, let's add it there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
hadoop 0.23.1 + hive 0.9: CliDriver tests failing
I am trying to build hive 0.9 against hadoop 0.23.1.
When I run the unit tests on the ql component for the TestCliDriver it results
in 3/4 of the tests failing.
By comparison, hive 0.9 against hadoop 0.20.2 passes all of these tests.
I have built against hadoop23 by making the following modifications in the
build.properties file:
hadoop.version=${hadoop-0.23.version}
hadoop.security.version=${hadoop-0.20S.version}
hadoop.mr.rev=23
Has anyone run against this problem before?
Is there a configuration parameter that I have not set properly (or some other
fix that I have overlooked)?
Thanks for your help,
chris
[jira] [Resolved] (HIVE-2860) TestNegativeCliDriver autolocal1.q fails on 0.23
[ https://issues.apache.org/jira/browse/HIVE-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2860. Resolution: Fixed Fix Version/s: 0.10.0 This is taken care of in HIVE-3275 TestNegativeCliDriver autolocal1.q fails on 0.23 Key: HIVE-2860 URL: https://issues.apache.org/jira/browse/HIVE-2860 Project: Hive Issue Type: Bug Components: Testing Infrastructure Affects Versions: 0.9.0 Reporter: Carl Steinbach Assignee: Carl Steinbach Fix For: 0.10.0 Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2860.D2253.1.patch, ASF.LICENSE.NOT.GRANTED--HIVE-2860.D2565.1.patch, HIVE-2860.D2253.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3411) Filter predicates on outer join overlapped on single alias is not handled properly
Navis created HIVE-3411:
---
Summary: Filter predicates on outer join overlapped on single
alias is not handled properly
Key: HIVE-3411
URL: https://issues.apache.org/jira/browse/HIVE-3411
Project: Hive
Issue Type: Sub-task
Components: Query Processor
Affects Versions: 0.10.0
Environment: ubuntu 10.10
Reporter: Navis
Assignee: Navis
Priority: Minor
Currently, join predicates on outer join are evaluated in join operator (or
HashSink for MapJoin) and the result value is tagged to end of each values(as a
boolean), which is used for joining values. But when predicates are overlapped
on single alias, all the predicates are evaluated with AND conjunction, which
makes invalid result.
For example with table a with values,
{noformat}
100 40
100 50
100 60
{noformat}
Query below has overlapped predicates on alias b, which is making all the
values on b are tagged with true(filtered)
{noformat}
select * from a right outer join a b on (a.key=b.key AND a.value=50 AND
b.value=50) left outer join a c on (b.key=c.key AND b.value=60 AND c.value=60);
NULLNULL100 40 NULLNULL
NULLNULL100 50 NULLNULL
NULLNULL100 60 NULLNULL
-- Join predicate
Join Operator
condition map:
Right Outer Join0 to 1
Left Outer Join1 to 2
condition expressions:
0 {VALUE._col0} {VALUE._col1}
1 {VALUE._col0} {VALUE._col1}
2 {VALUE._col0} {VALUE._col1}
filter predicates:
0
1 {(VALUE._col1 = 50)} {(VALUE._col1 = 60)}
2
{noformat}
but this should be
{noformat}
NULLNULL100 40 NULLNULL
100 50 100 50 NULLNULL
NULLNULL100 60 100 60
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442943#comment-13442943 ] Namit Jain commented on HIVE-3410: -- I will make the changes/comments. Kevin, should I call it OperatorDesc ? Changing the name in the future will not be that difficult, since eclipse should be able to rename it. Won't require going through all the code. All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3410.1.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3410: - Attachment: hive.3410.2.patch All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3410.1.patch, hive.3410.2.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3410) All operators's conf should inherit from a common class
[ https://issues.apache.org/jira/browse/HIVE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3410: - Status: Patch Available (was: Open) comments addressed All operators's conf should inherit from a common class --- Key: HIVE-3410 URL: https://issues.apache.org/jira/browse/HIVE-3410 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3410.1.patch, hive.3410.2.patch I faced this problem while working on HIVE-3086. Wanted to add a common interface to all the operator's confs. Currently, the operator signature is OperatorT extends Serializable, which makes it difficult to add more methods to T. Created a common interface SerializableCloneable, and now OperatorT extends SerializableCloneable. If we want to add more methods to SerializableCloneable in the future, it wont require changing so many files, so submitting it as a separate patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
