[jira] [Updated] (SPARK-14485) Task finished cause fetch failure when its executor has already been removed by driver

2016-06-06 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-14485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] iward updated SPARK-14485: -- Summary: Task finished cause fetch failure when its executor has already been removed by driver (was: Task fi

[jira] [Created] (SPARK-14485) Task finished cause fetch failure when its executor has already removed by driver

2016-04-08 Thread iward (JIRA)
iward created SPARK-14485: - Summary: Task finished cause fetch failure when its executor has already removed by driver Key: SPARK-14485 URL: https://issues.apache.org/jira/browse/SPARK-14485 Project: Spark

[jira] [Updated] (SPARK-12864) Fetch failure from AM restart

2016-04-01 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-12864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] iward updated SPARK-12864: -- Description: Currently, when max number of executor failures reached the *maxNumExecutorFailures*, *Applicati

[jira] [Updated] (SPARK-12864) Fetch failure from AM restart

2016-04-01 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-12864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] iward updated SPARK-12864: -- Description: Currently, when max number of executor failures reached the *maxNumExecutorFailures*, *Applicati

[jira] [Commented] (SPARK-12864) initialize executorIdCounter after ApplicationMaster killed for max number of executor failures reached

2016-01-19 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-12864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107859#comment-15107859 ] iward commented on SPARK-12864: --- The important point of the idea is to fix this conflict ex

[jira] [Commented] (SPARK-12864) initialize executorIdCounter after ApplicationMaster killed for max number of executor failures reached

2016-01-18 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-12864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106295#comment-15106295 ] iward commented on SPARK-12864: --- I don't think so. Why don't fix this conflict executor id

[jira] [Commented] (SPARK-12864) initialize executorIdCounter after ApplicationMaster killed for max number of executor failures reached

2016-01-18 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-12864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106129#comment-15106129 ] iward commented on SPARK-12864: --- Yeah, you are right. When AM is exited, All executors will

[jira] [Created] (SPARK-12864) initialize executorIdCounter after ApplicationMaster killed for max number of executor failures reached

2016-01-17 Thread iward (JIRA)
iward created SPARK-12864: - Summary: initialize executorIdCounter after ApplicationMaster killed for max number of executor failures reached Key: SPARK-12864 URL: https://issues.apache.org/jira/browse/SPARK-12864

[jira] [Commented] (SPARK-12125) pull out nondeterministic expressions from Join

2015-12-06 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044272#comment-15044272 ] iward commented on SPARK-12125: --- Ok,get.Thanks a lot. > pull out nondeterministic expressi

[jira] [Updated] (SPARK-12125) pull out nondeterministic expressions from Join

2015-12-03 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] iward updated SPARK-12125: -- Fix Version/s: 1.6.0 > pull out nondeterministic expressions from Join > --

[jira] [Created] (SPARK-12125) pull out nondeterministic expressions from Join

2015-12-03 Thread iward (JIRA)
iward created SPARK-12125: - Summary: pull out nondeterministic expressions from Join Key: SPARK-12125 URL: https://issues.apache.org/jira/browse/SPARK-12125 Project: Spark Issue Type: Bug Affects

[jira] [Created] (SPARK-11021) SparkSQL cli throws exception when using with Hive 0.12 metastore in spark-1.5.0 version

2015-10-08 Thread iward (JIRA)
iward created SPARK-11021: - Summary: SparkSQL cli throws exception when using with Hive 0.12 metastore in spark-1.5.0 version Key: SPARK-11021 URL: https://issues.apache.org/jira/browse/SPARK-11021 Project: S

[jira] [Commented] (SPARK-3720) support ORC in spark sql

2015-03-23 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377155#comment-14377155 ] iward commented on SPARK-3720: -- [~zhanzhang], I see. since the patch is delayed, so we can't

[jira] [Comment Edited] (SPARK-3720) support ORC in spark sql

2015-03-23 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375590#comment-14375590 ] iward edited comment on SPARK-3720 at 3/23/15 9:10 AM: --- hi,[~zhzhan]

[jira] [Comment Edited] (SPARK-3720) support ORC in spark sql

2015-03-23 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375590#comment-14375590 ] iward edited comment on SPARK-3720 at 3/23/15 9:05 AM: --- hi,[~zhzhan]

[jira] [Commented] (SPARK-3720) support ORC in spark sql

2015-03-23 Thread iward (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375590#comment-14375590 ] iward commented on SPARK-3720: -- hi,Zhan Zhang , I have the same problem.And I just contact or