[jira] [Created] (SPARK-3611) Show number of cores for each executor in application web UI

Matei Zaharia created SPARK-3611: Summary: Show number of cores for each executor in application web UI Key: SPARK-3611 URL: https://issues.apache.org/jira/browse/SPARK-3611 Project: Spark

[jira] [Created] (SPARK-3612) Executor shouldn't quit if heartbeat message fails to reach the driver

Reynold Xin created SPARK-3612: -- Summary: Executor shouldn't quit if heartbeat message fails to reach the driver Key: SPARK-3612 URL: https://issues.apache.org/jira/browse/SPARK-3612 Project: Spark

[jira] [Commented] (SPARK-3612) Executor shouldn't quit if heartbeat message fails to reach the driver

[ https://issues.apache.org/jira/browse/SPARK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141807#comment-14141807 ] Reynold Xin commented on SPARK-3612: [~andrewor14] [~sandyryza] any comment on this? I

[jira] [Created] (SPARK-3613) Don't record the size of each shuffle block for large jobs

Reynold Xin created SPARK-3613: -- Summary: Don't record the size of each shuffle block for large jobs Key: SPARK-3613 URL: https://issues.apache.org/jira/browse/SPARK-3613 Project: Spark Issue

[jira] [Commented] (SPARK-3613) Don't record the size of each shuffle block for large jobs

[ https://issues.apache.org/jira/browse/SPARK-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141870#comment-14141870 ] Apache Spark commented on SPARK-3613: - User 'rxin' has created a pull request for this

[jira] [Updated] (SPARK-3608) Spark EC2 Script does not correctly break when AWS tagging succeeds.

[ https://issues.apache.org/jira/browse/SPARK-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin updated SPARK-3608: --- Assignee: Vida Ha Spark EC2 Script does not correctly break when AWS tagging succeeds.

[jira] [Resolved] (SPARK-3608) Spark EC2 Script does not correctly break when AWS tagging succeeds.

[ https://issues.apache.org/jira/browse/SPARK-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin resolved SPARK-3608. Resolution: Fixed Fix Version/s: 1.2.0 Target Version/s: 1.2.0 Spark EC2 Script

[jira] [Commented] (SPARK-3562) Periodic cleanup event logs

[ https://issues.apache.org/jira/browse/SPARK-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141876#comment-14141876 ] Apache Spark commented on SPARK-3562: - User 'viper-kun' has created a pull request for

[jira] [Commented] (SPARK-3612) Executor shouldn't quit if heartbeat message fails to reach the driver

[ https://issues.apache.org/jira/browse/SPARK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142006#comment-14142006 ] Sandy Ryza commented on SPARK-3612: --- Yeah, we should catch this. Will post a patch.

[jira] [Updated] (SPARK-3614) Filter on minimum occurrences of a term in IDF

[ https://issues.apache.org/jira/browse/SPARK-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jatinpreet Singh updated SPARK-3614: Description: The IDF class in MLlib does not provide the capability of defining a minimum

[jira] [Updated] (SPARK-3614) Filter on minimum occurrences of a term in IDF

[ https://issues.apache.org/jira/browse/SPARK-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jatinpreet Singh updated SPARK-3614: Description: The IDF class in MLlib does not provide the capability of defining a minimum

[jira] [Updated] (SPARK-3614) Filter on minimum occurrences of a term in IDF

[ https://issues.apache.org/jira/browse/SPARK-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jatinpreet Singh updated SPARK-3614: Description: The IDF class in MLlib does not provide the capability of defining a minimum

[jira] [Created] (SPARK-3615) Kafka test should not hard code Zookeeper port

Patrick Wendell created SPARK-3615: -- Summary: Kafka test should not hard code Zookeeper port Key: SPARK-3615 URL: https://issues.apache.org/jira/browse/SPARK-3615 Project: Spark Issue Type:

[jira] [Updated] (SPARK-3610) Unable to load app logs for MLLib programs in history server

[ https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-3610: --- Priority: Critical (was: Major) Unable to load app logs for MLLib programs in history

[jira] [Updated] (SPARK-3610) History server log name should not be based on user input

[ https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-3610: --- Description: Right now we don't have a Original bug report: The default log files for the

[jira] [Updated] (SPARK-3610) History server log name should not be based on user input

[ https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-3610: --- Description: Right now we use the user-defined application name when creating the logging

[jira] [Updated] (SPARK-3610) History server log name should not be based on user input

[ https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-3610: --- Description: Right now we use the user-defined application name when creating the logging

[jira] [Updated] (SPARK-3610) History server log name should not be based on user input

[ https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Rosen updated SPARK-3610: -- Component/s: Web UI History server log name should not be based on user input

[jira] [Updated] (SPARK-3610) History server log name should not be based on user input

[ https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-3610: --- Fix Version/s: (was: 1.1.0) History server log name should not be based on user input

[jira] [Updated] (SPARK-3610) History server log name should not be based on user input

[ https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-3610: --- Component/s: (was: Web UI) Target Version/s: 1.2.0 History server log name

[jira] [Resolved] (SPARK-3609) Add sizeInBytes statistics to Limit operator

[ https://issues.apache.org/jira/browse/SPARK-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust resolved SPARK-3609. - Resolution: Fixed Fix Version/s: 1.2.0 Issue resolved by pull request 2468

[jira] [Created] (SPARK-3617) Configurable case sensitivity

Michael Armbrust created SPARK-3617: --- Summary: Configurable case sensitivity Key: SPARK-3617 URL: https://issues.apache.org/jira/browse/SPARK-3617 Project: Spark Issue Type: New Feature

[jira] [Created] (SPARK-3618) Store analyzed plans for temp tables

Michael Armbrust created SPARK-3618: --- Summary: Store analyzed plans for temp tables Key: SPARK-3618 URL: https://issues.apache.org/jira/browse/SPARK-3618 Project: Spark Issue Type: Bug

[jira] [Resolved] (SPARK-2274) spark SQL query hang up sometimes

[ https://issues.apache.org/jira/browse/SPARK-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust resolved SPARK-2274. - Resolution: Fixed Fix Version/s: 1.1.0 The attached query is using a left outer

[jira] [Updated] (SPARK-3267) Deadlock between ScalaReflectionLock and Data type initialization

[ https://issues.apache.org/jira/browse/SPARK-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust updated SPARK-3267: Assignee: (was: Michael Armbrust) Deadlock between ScalaReflectionLock and Data type

[jira] [Resolved] (SPARK-3414) Case insensitivity breaks when unresolved relation contains attributes with uppercase letters in their names

[ https://issues.apache.org/jira/browse/SPARK-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust resolved SPARK-3414. - Resolution: Fixed Issue resolved by pull request 2382

[jira] [Created] (SPARK-3619) Upgrade to Mesos 0.21 to work around MESOS-1688

Matei Zaharia created SPARK-3619: Summary: Upgrade to Mesos 0.21 to work around MESOS-1688 Key: SPARK-3619 URL: https://issues.apache.org/jira/browse/SPARK-3619 Project: Spark Issue Type:

[jira] [Commented] (SPARK-3616) Add Selenium tests to Web UI

[ https://issues.apache.org/jira/browse/SPARK-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142244#comment-14142244 ] Apache Spark commented on SPARK-3616: - User 'JoshRosen' has created a pull request for

[jira] [Commented] (SPARK-3604) unbounded recursion in getNumPartitions triggers stack overflow for large UnionRDD

[ https://issues.apache.org/jira/browse/SPARK-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142257#comment-14142257 ] Patrick Wendell commented on SPARK-3604: After looking at the PR - I think the

[jira] [Comment Edited] (SPARK-3604) unbounded recursion in getNumPartitions triggers stack overflow for large UnionRDD

[ https://issues.apache.org/jira/browse/SPARK-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142257#comment-14142257 ] Patrick Wendell edited comment on SPARK-3604 at 9/21/14 12:35 AM:

[jira] [Created] (SPARK-3620) Refactor parameter handling code for spark-submit

Dale Richardson created SPARK-3620: -- Summary: Refactor parameter handling code for spark-submit Key: SPARK-3620 URL: https://issues.apache.org/jira/browse/SPARK-3620 Project: Spark Issue

[jira] [Updated] (SPARK-3620) Refactor config option handling code for spark-submit

[ https://issues.apache.org/jira/browse/SPARK-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Richardson updated SPARK-3620: --- Summary: Refactor config option handling code for spark-submit (was: Refactor parameter

[jira] [Commented] (SPARK-3247) Improved support for external data sources

[ https://issues.apache.org/jira/browse/SPARK-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142277#comment-14142277 ] Apache Spark commented on SPARK-3247: - User 'marmbrus' has created a pull request for

[jira] [Resolved] (SPARK-3599) Avoid loading and printing properties file content frequently

[ https://issues.apache.org/jira/browse/SPARK-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell resolved SPARK-3599. Resolution: Fixed Assignee: WangTaoTheTonic Avoid loading and printing properties

[jira] [Commented] (SPARK-1966) Cannot cancel tasks running locally

[ https://issues.apache.org/jira/browse/SPARK-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142334#comment-14142334 ] Josh Rosen commented on SPARK-1966: --- Actually, scratch that; it wasn't an issue since

[jira] [Commented] (SPARK-1597) Add a version of reduceByKey that takes the Partitioner as a second argument

[ https://issues.apache.org/jira/browse/SPARK-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142335#comment-14142335 ] Patrick Wendell commented on SPARK-1597: See relevant comment here:

[jira] [Created] (SPARK-3621) Provide a way to broadcast an RDD (instead of just a variable made of the RDD) so that a job can access

Xuefu Zhang created SPARK-3621: -- Summary: Provide a way to broadcast an RDD (instead of just a variable made of the RDD) so that a job can access Key: SPARK-3621 URL: https://issues.apache.org/jira/browse/SPARK-3621

[jira] [Created] (SPARK-3622) Provide a custom transformation that can output multiple RDDs

Xuefu Zhang created SPARK-3622: -- Summary: Provide a custom transformation that can output multiple RDDs Key: SPARK-3622 URL: https://issues.apache.org/jira/browse/SPARK-3622 Project: Spark

[jira] [Updated] (SPARK-2630) Input data size of CoalescedRDD is incorrect

[ https://issues.apache.org/jira/browse/SPARK-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-2630: --- Target Version/s: 1.2.0 (was: 1.1.0) Input data size of CoalescedRDD is incorrect

[jira] [Updated] (SPARK-2630) Input data size of CoalescedRDD is incorrect

[ https://issues.apache.org/jira/browse/SPARK-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-2630: --- Assignee: Andrew Ash Input data size of CoalescedRDD is incorrect

[jira] [Updated] (SPARK-2630) Input data size of CoalescedRDD is incorrect

[ https://issues.apache.org/jira/browse/SPARK-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Wendell updated SPARK-2630: --- Priority: Blocker (was: Critical) Input data size of CoalescedRDD is incorrect