[jira] [Commented] (TEZ-3030) java.lang.NoClassDefFoundError: org/apache/hadoop/mapred/MRVersion

2016-01-14 Thread YuanXiaoLong (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097942#comment-15097942 ] YuanXiaoLong commented on TEZ-3030: --- @gewenhui it works, thanks > java.lang.NoClassDefFoundError:

[jira] [Updated] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-3037: - Attachment: TEZ-3037.2.branch-0.7.patch > History URL should be set regardless of which history logging

[jira] [Commented] (TEZ-2937) Can Processor.close() be called after closing inputs and outputs?

2016-01-14 Thread Bikas Saha (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099175#comment-15099175 ] Bikas Saha commented on TEZ-2937: - lgtm. Unrelated to the patch, but maybe the llap version of

[jira] [Updated] (TEZ-3032) DAG start time getting logged using system time instead of recorded time in startTime field

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-3032: - Fix Version/s: (was: 0.7.1) > DAG start time getting logged using system time instead of recorded time

[jira] [Updated] (TEZ-3032) DAG start time getting logged using system time instead of recorded time in startTime field

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-3032: - Affects Version/s: 0.8.1-alpha > DAG start time getting logged using system time instead of recorded time

Failed: TEZ-2937 PreCommit Build #1424

2016-01-14 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/TEZ-2937 Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1424/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Commented] (TEZ-2937) Can Processor.close() be called after closing inputs and outputs?

2016-01-14 Thread TezQA (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099219#comment-15099219 ] TezQA commented on TEZ-2937: {color:red}-1 overall{color}. Here are the results of testing the latest

[jira] [Commented] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread TezQA (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098706#comment-15098706 ] TezQA commented on TEZ-3037: {color:red}-1 overall{color}. Here are the results of testing the latest

[jira] [Commented] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098720#comment-15098720 ] Hitesh Shah commented on TEZ-3037: -- Fixed findbugs warning in patch 2. Thanks for the review [~bikassaha].

[jira] [Updated] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-3037: - Attachment: TEZ-3037.2.patch > History URL should be set regardless of which history logging service is >

Failed: TEZ-3037 PreCommit Build #1422

2016-01-14 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/TEZ-3037 Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1422/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Commented] (TEZ-2164) Shade the guava version used by Tez and move to guava-18

2016-01-14 Thread Rajat Jain (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101216#comment-15101216 ] Rajat Jain commented on TEZ-2164: - Just for my understanding. Why can't we just apply {{relocation}} using

[jira] [Updated] (TEZ-3032) DAG start time getting logged using system time instead of recorded time in startTime field

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-3032: - Attachment: TEZ-3032.addendum.patch Minor fix for finish time. > DAG start time getting logged using

[jira] [Updated] (TEZ-3032) DAG start time getting logged using system time instead of recorded time in startTime field

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-3032: - Attachment: TEZ-3032.1.patch > DAG start time getting logged using system time instead of recorded time in

[jira] [Commented] (TEZ-3032) DAG start time getting logged using system time instead of recorded time in startTime field

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098872#comment-15098872 ] Hitesh Shah commented on TEZ-3032: -- [~sseth] review please. Trivial patch. > DAG start time getting

[jira] [Commented] (TEZ-3032) DAG start time getting logged using system time instead of recorded time in startTime field

2016-01-14 Thread Siddharth Seth (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098930#comment-15098930 ] Siddharth Seth commented on TEZ-3032: - +1. Looks good. > DAG start time getting logged using system

[jira] [Updated] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-3037: - Attachment: TEZ-3037.1.patch [~bikassaha] please review > History URL should be set regardless of which

[jira] [Assigned] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah reassigned TEZ-3037: Assignee: Hitesh Shah > History URL should be set regardless of which history logging service is >

[jira] [Commented] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread Bikas Saha (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098618#comment-15098618 ] Bikas Saha commented on TEZ-3037: - lgtm. > History URL should be set regardless of which history logging

[jira] [Resolved] (TEZ-2696) Rename TaskAttemptListener and associated classes to TaskCommunicatorManager

2016-01-14 Thread Siddharth Seth (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth resolved TEZ-2696. - Resolution: Done Resolved elsewhere. > Rename TaskAttemptListener and associated classes to

[jira] [Commented] (TEZ-3037) History URL should be set regardless of which history logging service is enabled

2016-01-14 Thread TezQA (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098975#comment-15098975 ] TezQA commented on TEZ-3037: {color:red}-1 overall{color}. Here are the results of testing the latest

Failed: TEZ-3037 PreCommit Build #1423

2016-01-14 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/TEZ-3037 Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1423/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Updated] (TEZ-2937) Can Processor.close() be called after closing inputs and outputs?

2016-01-14 Thread Jonathan Eagles (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated TEZ-2937: - Attachment: TEZ-2937.1.patch Been running with the above patch since mid-November. > Can