[jira] [Commented] (SPARK-24502) flaky test: UnsafeRowSerializerSuite

[ https://issues.apache.org/jira/browse/SPARK-24502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574410#comment-16574410 ] Paul Praet commented on SPARK-24502: Find it hard to believe above pull requests were accepted,

[jira] [Assigned] (SPARK-25069) Using UnsafeAlignedOffset to make the entire record of 8 byte Items aligned like which is used in UnsafeExternalSorter

[ https://issues.apache.org/jira/browse/SPARK-25069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25069: Assignee: (was: Apache Spark) > Using UnsafeAlignedOffset to make the entire record

[jira] [Commented] (SPARK-25069) Using UnsafeAlignedOffset to make the entire record of 8 byte Items aligned like which is used in UnsafeExternalSorter

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

[jira] [Assigned] (SPARK-25069) Using UnsafeAlignedOffset to make the entire record of 8 byte Items aligned like which is used in UnsafeExternalSorter

[ https://issues.apache.org/jira/browse/SPARK-25069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25069: Assignee: Apache Spark > Using UnsafeAlignedOffset to make the entire record of 8 byte

[jira] [Updated] (SPARK-25065) Provide a way to add a custom logging configuration file.

[ https://issues.apache.org/jira/browse/SPARK-25065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Sharma updated SPARK-25065: Description: Currently, when running in kubernetes mode, it sets necessary configuration

[jira] [Updated] (SPARK-25065) Provide a way to add a custom logging configuration file.

[ https://issues.apache.org/jira/browse/SPARK-25065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Sharma updated SPARK-25065: Description: Currently, when running in kubernetes mode, it sets necessary configuration

[jira] [Updated] (SPARK-25067) Active tasks exceed total cores of an executor in WebUI

[ https://issues.apache.org/jira/browse/SPARK-25067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] StanZhai updated SPARK-25067: - Attachment: 1533128203469_2.png > Active tasks exceed total cores of an executor in WebUI >

[jira] [Commented] (SPARK-25068) High-order function: exists(array, function) → boolean

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

[jira] [Assigned] (SPARK-25068) High-order function: exists(array, function) → boolean

[ https://issues.apache.org/jira/browse/SPARK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25068: Assignee: Apache Spark (was: Takuya Ueshin) > High-order function: exists(array,

[jira] [Created] (SPARK-25070) BlockFetchingListener#onBlockFetchSuccess throw "java.util.NoSuchElementException: key not found: shuffle_8_68_113" on ShuffleBlockFetcherIterator caused stage hang lon

DENG FEI created SPARK-25070: Summary: BlockFetchingListener#onBlockFetchSuccess throw "java.util.NoSuchElementException: key not found: shuffle_8_68_113" on ShuffleBlockFetcherIterator caused stage hang long time Key: SPARK-25070

[jira] [Assigned] (SPARK-25064) Total Tasks in WebUI does not match Active+Failed+Complete Tasks

[ https://issues.apache.org/jira/browse/SPARK-25064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25064: Assignee: (was: Apache Spark) > Total Tasks in WebUI does not match

[jira] [Commented] (SPARK-25064) Total Tasks in WebUI does not match Active+Failed+Complete Tasks

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

[jira] [Assigned] (SPARK-25064) Total Tasks in WebUI does not match Active+Failed+Complete Tasks

[ https://issues.apache.org/jira/browse/SPARK-25064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25064: Assignee: Apache Spark > Total Tasks in WebUI does not match Active+Failed+Complete

[jira] [Created] (SPARK-25069) Using UnsafeAlignedOffset to make the entire record of 8 byte Items aligned like which is used in UnsafeExternalSorter

eaton created SPARK-25069: - Summary: Using UnsafeAlignedOffset to make the entire record of 8 byte Items aligned like which is used in UnsafeExternalSorter Key: SPARK-25069 URL:

[jira] [Updated] (SPARK-25064) Total Tasks in WebUI does not match Active+Failed+Complete Tasks

[ https://issues.apache.org/jira/browse/SPARK-25064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] StanZhai updated SPARK-25064: - Attachment: 1533128402933_3.png > Total Tasks in WebUI does not match Active+Failed+Complete Tasks >

[jira] [Created] (SPARK-25068) High-order function: exists(array, function) → boolean

Takuya Ueshin created SPARK-25068: - Summary: High-order function: exists(array, function) → boolean Key: SPARK-25068 URL: https://issues.apache.org/jira/browse/SPARK-25068 Project: Spark

[jira] [Assigned] (SPARK-25068) High-order function: exists(array, function) → boolean

[ https://issues.apache.org/jira/browse/SPARK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25068: Assignee: Takuya Ueshin (was: Apache Spark) > High-order function: exists(array,

[jira] [Assigned] (SPARK-24703) Unable to multiply calendar interval

[ https://issues.apache.org/jira/browse/SPARK-24703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-24703: Assignee: (was: Apache Spark) > Unable to multiply calendar interval >

[jira] [Assigned] (SPARK-24703) Unable to multiply calendar interval

[ https://issues.apache.org/jira/browse/SPARK-24703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-24703: Assignee: Apache Spark > Unable to multiply calendar interval >

[jira] [Commented] (SPARK-24703) Unable to multiply calendar interval

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

[jira] [Updated] (SPARK-25067) Active tasks exceed total cores of an executor in WebUI

[ https://issues.apache.org/jira/browse/SPARK-25067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] StanZhai updated SPARK-25067: - Attachment: WechatIMG1.jpeg > Active tasks exceed total cores of an executor in WebUI >

[jira] [Updated] (SPARK-25070) BlockFetchingListener#onBlockFetchSuccess throw "java.util.NoSuchElementException: key not found: shuffle_8_68_113" on ShuffleBlockFetcherIterator caused stage hang lon

[ https://issues.apache.org/jira/browse/SPARK-25070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DENG FEI updated SPARK-25070: - Description: The task fetch shuffle block success, but failed onBlockFetchSuccess, lead the task hang

[jira] [Created] (SPARK-25067) Active tasks exceed total cores of an executor in WebUI

StanZhai created SPARK-25067: Summary: Active tasks exceed total cores of an executor in WebUI Key: SPARK-25067 URL: https://issues.apache.org/jira/browse/SPARK-25067 Project: Spark Issue Type:

[jira] [Resolved] (SPARK-24042) High-order function: zip_with_index

[ https://issues.apache.org/jira/browse/SPARK-24042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny resolved SPARK-24042. --- Resolution: Won't Fix > High-order function: zip_with_index >

[jira] [Commented] (SPARK-25065) Provide a way to add a custom logging configuration file.

[ https://issues.apache.org/jira/browse/SPARK-25065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574414#comment-16574414 ] Prashant Sharma commented on SPARK-25065: - One work around is to edit Dockerfile and copy

[jira] [Created] (SPARK-25066) Provide Spark R image for deploying Spark on kubernetes.

Prashant Sharma created SPARK-25066: --- Summary: Provide Spark R image for deploying Spark on kubernetes. Key: SPARK-25066 URL: https://issues.apache.org/jira/browse/SPARK-25066 Project: Spark

[jira] [Resolved] (SPARK-25055) MessageWithHeader transfer ByteBuffer from Netty's CompositeByteBuf many times

[ https://issues.apache.org/jira/browse/SPARK-25055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DENG FEI resolved SPARK-25055. -- Resolution: Duplicate > MessageWithHeader transfer ByteBuffer from Netty's CompositeByteBuf many

[jira] [Created] (SPARK-25065) Provide a way to add a custom logging configuration file.

Prashant Sharma created SPARK-25065: --- Summary: Provide a way to add a custom logging configuration file. Key: SPARK-25065 URL: https://issues.apache.org/jira/browse/SPARK-25065 Project: Spark

[jira] [Created] (SPARK-25064) Total Tasks in WebUI does not match Active+Failed+Complete Tasks

StanZhai created SPARK-25064: Summary: Total Tasks in WebUI does not match Active+Failed+Complete Tasks Key: SPARK-25064 URL: https://issues.apache.org/jira/browse/SPARK-25064 Project: Spark

[jira] [Updated] (SPARK-25071) BuildSide is coming not as expected with join queries

[ https://issues.apache.org/jira/browse/SPARK-25071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Anubhava updated SPARK-25071: --- Description: *BuildSide is not coming as expected.* Pre-requisites: *CBO is set as true & 

[jira] [Commented] (SPARK-25044) Address translation of LMF closure primitive args to Object in Scala 2.12

[ https://issues.apache.org/jira/browse/SPARK-25044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574841#comment-16574841 ] Sean Owen commented on SPARK-25044: --- I tried this – it's not hard – but the implementation method

[jira] [Updated] (SPARK-25071) BuildSide is coming not as expected with join queries

[ https://issues.apache.org/jira/browse/SPARK-25071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Anubhava updated SPARK-25071: --- Attachment: SPARK-25071_IMG2.PNG > BuildSide is coming not as expected with join queries >

[jira] [Commented] (SPARK-25032) Create table is failing, after dropping the database . It is not falling back to default database

[ https://issues.apache.org/jira/browse/SPARK-25032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574754#comment-16574754 ] sandeep katta commented on SPARK-25032: --- I will be looking into this.   Solution: 1)Don't allow

[jira] [Assigned] (SPARK-25047) Can't assign SerializedLambda to scala.Function1 in deserialization of BucketedRandomProjectionLSHModel

[ https://issues.apache.org/jira/browse/SPARK-25047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen reassigned SPARK-25047: - Assignee: Sean Owen > Can't assign SerializedLambda to scala.Function1 in deserialization of

[jira] [Commented] (SPARK-25073) Spark-submit on Yarn Task : When the yarn.nodemanager.resource.memory-mb and/or yarn.scheduler.maximum-allocation-mb is insufficient, Spark always reports an error req

[ https://issues.apache.org/jira/browse/SPARK-25073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574864#comment-16574864 ] Sujith commented on SPARK-25073: Seems to be you are right, Message is bit misleading to the user. As

[jira] [Commented] (SPARK-12449) Pushing down arbitrary logical plans to data sources

[ https://issues.apache.org/jira/browse/SPARK-12449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574770#comment-16574770 ] Johannes Zillmann commented on SPARK-12449: --- I'm a bit confused. Reading

[jira] [Created] (SPARK-25074) Implement maxNumConcurrentTasks() in MesosFineGrainedSchedulerBackend

Jiang Xingbo created SPARK-25074: Summary: Implement maxNumConcurrentTasks() in MesosFineGrainedSchedulerBackend Key: SPARK-25074 URL: https://issues.apache.org/jira/browse/SPARK-25074 Project: Spark

[jira] [Assigned] (SPARK-23415) BufferHolderSparkSubmitSuite is flaky

[ https://issues.apache.org/jira/browse/SPARK-23415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-23415: --- Assignee: Kazuaki Ishizaki > BufferHolderSparkSubmitSuite is flaky >

[jira] [Resolved] (SPARK-23415) BufferHolderSparkSubmitSuite is flaky

[ https://issues.apache.org/jira/browse/SPARK-23415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan resolved SPARK-23415. - Resolution: Fixed Fix Version/s: 2.4.0 Issue resolved by pull request 20636

[jira] [Updated] (SPARK-25071) BuildSide is coming not as expected with join queries

[ https://issues.apache.org/jira/browse/SPARK-25071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Anubhava updated SPARK-25071: --- Attachment: (was: SPARK-25071_IMG2.PNG) > BuildSide is coming not as expected with join

[jira] [Created] (SPARK-25073) Spark-submit on Yarn Task : When the yarn.nodemanager.resource.memory-mb and/or yarn.scheduler.maximum-allocation-mb is insufficient, Spark always reports an error reque

vivek kumar created SPARK-25073: --- Summary: Spark-submit on Yarn Task : When the yarn.nodemanager.resource.memory-mb and/or yarn.scheduler.maximum-allocation-mb is insufficient, Spark always reports an error request to adjust

[jira] [Comment Edited] (SPARK-25032) Create table is failing, after dropping the database . It is not falling back to default database

[ https://issues.apache.org/jira/browse/SPARK-25032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574754#comment-16574754 ] sandeep katta edited comment on SPARK-25032 at 8/9/18 12:16 PM: I will

[jira] [Commented] (SPARK-25075) Build and test Spark against Scala 2.13

[ https://issues.apache.org/jira/browse/SPARK-25075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574839#comment-16574839 ] Guillaume Massé commented on SPARK-25075: - Scala 2.13 is currently in the milestone phases (We

[jira] [Created] (SPARK-25071) BuildSide is coming not as expected with join queries

Ayush Anubhava created SPARK-25071: -- Summary: BuildSide is coming not as expected with join queries Key: SPARK-25071 URL: https://issues.apache.org/jira/browse/SPARK-25071 Project: Spark

[jira] [Created] (SPARK-25072) PySpark custom Row class can be given extra parameters

Jan-Willem van der Sijp created SPARK-25072: --- Summary: PySpark custom Row class can be given extra parameters Key: SPARK-25072 URL: https://issues.apache.org/jira/browse/SPARK-25072 Project:

[jira] [Updated] (SPARK-25073) Spark-submit on Yarn Task : When the yarn.nodemanager.resource.memory-mb and/or yarn.scheduler.maximum-allocation-mb is insufficient, Spark always reports an error reque

[ https://issues.apache.org/jira/browse/SPARK-25073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vivek kumar updated SPARK-25073: Description: When the yarn.nodemanager.resource.memory-mb and/or

[jira] [Resolved] (SPARK-25047) Can't assign SerializedLambda to scala.Function1 in deserialization of BucketedRandomProjectionLSHModel

[ https://issues.apache.org/jira/browse/SPARK-25047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-25047. --- Resolution: Fixed Fix Version/s: 2.4.0 Issue resolved by pull request 22032

[jira] [Created] (SPARK-25075) Build and test Spark against Scala 2.13

Guillaume Massé created SPARK-25075: --- Summary: Build and test Spark against Scala 2.13 Key: SPARK-25075 URL: https://issues.apache.org/jira/browse/SPARK-25075 Project: Spark Issue Type:

[jira] [Resolved] (SPARK-25054) Enable MetricsServlet sink for Executor

[ https://issues.apache.org/jira/browse/SPARK-25054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lantao Jin resolved SPARK-25054. Resolution: Won't Fix > Enable MetricsServlet sink for Executor >

[jira] [Closed] (SPARK-25054) Enable MetricsServlet sink for Executor

[ https://issues.apache.org/jira/browse/SPARK-25054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lantao Jin closed SPARK-25054. -- > Enable MetricsServlet sink for Executor > --- > >

[jira] [Commented] (SPARK-23207) Shuffle+Repartition on an DataFrame could lead to incorrect answers

[ https://issues.apache.org/jira/browse/SPARK-23207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574956#comment-16574956 ] Thomas Graves commented on SPARK-23207: --- ok, I guess I disagree with that. Any correctness bug is

[jira] [Commented] (SPARK-24502) flaky test: UnsafeRowSerializerSuite

[ https://issues.apache.org/jira/browse/SPARK-24502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574908#comment-16574908 ] Wenchen Fan commented on SPARK-24502: - There is no resource leakage. Users need to manage the active

[jira] [Resolved] (SPARK-25063) Rename class KnowNotNull to KnownNotNull

[ https://issues.apache.org/jira/browse/SPARK-25063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li resolved SPARK-25063. - Resolution: Fixed Assignee: Maryann Xue Fix Version/s: 2.4.0 > Rename class KnowNotNull

[jira] [Commented] (SPARK-24502) flaky test: UnsafeRowSerializerSuite

[ https://issues.apache.org/jira/browse/SPARK-24502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575026#comment-16575026 ] Paul Praet commented on SPARK-24502: We are only creating SparkSessions with a

[jira] [Commented] (SPARK-25077) Delete unused variable in WindowExec

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

[jira] [Assigned] (SPARK-25077) Delete unused variable in WindowExec

[ https://issues.apache.org/jira/browse/SPARK-25077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25077: Assignee: (was: Apache Spark) > Delete unused variable in WindowExec >

[jira] [Assigned] (SPARK-25077) Delete unused variable in WindowExec

[ https://issues.apache.org/jira/browse/SPARK-25077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25077: Assignee: Apache Spark > Delete unused variable in WindowExec >

[jira] [Commented] (SPARK-23207) Shuffle+Repartition on an DataFrame could lead to incorrect answers

[ https://issues.apache.org/jira/browse/SPARK-23207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574886#comment-16574886 ] Thomas Graves commented on SPARK-23207: --- [~jiangxb1987] ^ > Shuffle+Repartition on an DataFrame

[jira] [Commented] (SPARK-12449) Pushing down arbitrary logical plans to data sources

[ https://issues.apache.org/jira/browse/SPARK-12449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575044#comment-16575044 ] Kyle Prifogle commented on SPARK-12449: --- [~oae]  as far as I can tell the issue lives on here: 

[jira] [Created] (SPARK-25076) SQLConf should not be retrieved from a stopped SparkSession

Wenchen Fan created SPARK-25076: --- Summary: SQLConf should not be retrieved from a stopped SparkSession Key: SPARK-25076 URL: https://issues.apache.org/jira/browse/SPARK-25076 Project: Spark

[jira] [Commented] (SPARK-23207) Shuffle+Repartition on an DataFrame could lead to incorrect answers

[ https://issues.apache.org/jira/browse/SPARK-23207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574903#comment-16574903 ] Jiang Xingbo commented on SPARK-23207: -- This affects the 2.2 and lower versions, the reason why we

[jira] [Assigned] (SPARK-25076) SQLConf should not be retrieved from a stopped SparkSession

[ https://issues.apache.org/jira/browse/SPARK-25076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25076: Assignee: Apache Spark (was: Wenchen Fan) > SQLConf should not be retrieved from a

[jira] [Assigned] (SPARK-25076) SQLConf should not be retrieved from a stopped SparkSession

[ https://issues.apache.org/jira/browse/SPARK-25076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25076: Assignee: Wenchen Fan (was: Apache Spark) > SQLConf should not be retrieved from a

[jira] [Commented] (SPARK-25076) SQLConf should not be retrieved from a stopped SparkSession

[ https://issues.apache.org/jira/browse/SPARK-25076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574915#comment-16574915 ] Apache Spark commented on SPARK-25076: -- User 'cloud-fan' has created a pull request for this issue:

[jira] [Created] (SPARK-25077) Delete unused variable in WindowExec

Li Yuanjian created SPARK-25077: --- Summary: Delete unused variable in WindowExec Key: SPARK-25077 URL: https://issues.apache.org/jira/browse/SPARK-25077 Project: Spark Issue Type: Improvement

[jira] [Commented] (SPARK-24502) flaky test: UnsafeRowSerializerSuite

[ https://issues.apache.org/jira/browse/SPARK-24502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575642#comment-16575642 ] Wenchen Fan commented on SPARK-24502: - This is enough. The places you need to pay attention to is

[jira] [Updated] (SPARK-23243) Shuffle+Repartition on an RDD could lead to incorrect answers

[ https://issues.apache.org/jira/browse/SPARK-23243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan updated SPARK-23243: Labels: correctness (was: ) > Shuffle+Repartition on an RDD could lead to incorrect answers >

[jira] [Closed] (SPARK-25052) Is there any possibility that spark structured streaming generate duplicates in the output?

[ https://issues.apache.org/jira/browse/SPARK-25052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla closed SPARK-25052. --- > Is there any possibility that spark structured streaming generate duplicates

[jira] [Created] (SPARK-25078) Standalone cluster mode does not work with spark.authenticate.secret

Imran Rashid created SPARK-25078: Summary: Standalone cluster mode does not work with spark.authenticate.secret Key: SPARK-25078 URL: https://issues.apache.org/jira/browse/SPARK-25078 Project: Spark

[jira] [Commented] (SPARK-22634) Update Bouncy castle dependency

[ https://issues.apache.org/jira/browse/SPARK-22634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575066#comment-16575066 ] Sean Owen commented on SPARK-22634: --- That text is part of Netty's NOTICE file, which must be

[jira] [Updated] (SPARK-25036) Scala 2.12 issues: Compilation error with sbt

[ https://issues.apache.org/jira/browse/SPARK-25036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kazuaki Ishizaki updated SPARK-25036: - Description: When compiling with sbt, the following errors occur: There are -two-

[jira] [Commented] (SPARK-25036) Scala 2.12 issues: Compilation error with sbt

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

[jira] [Commented] (SPARK-23874) Upgrade apache/arrow to 0.10.0

[ https://issues.apache.org/jira/browse/SPARK-23874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575170#comment-16575170 ] shane knapp commented on SPARK-23874: - this issue depends on this:  

[jira] [Created] (SPARK-25079) [PYTHON] upgrade python 3.4 -> 3.5

shane knapp created SPARK-25079: --- Summary: [PYTHON] upgrade python 3.4 -> 3.5 Key: SPARK-25079 URL: https://issues.apache.org/jira/browse/SPARK-25079 Project: Spark Issue Type: Improvement

[jira] [Commented] (SPARK-25036) Scala 2.12 issues: Compilation error with sbt

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

[jira] [Commented] (SPARK-25024) Update mesos documentation to be clear about security supported

[ https://issues.apache.org/jira/browse/SPARK-25024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575134#comment-16575134 ] Arthur Rand commented on SPARK-25024: - Just to chime in here. Unless a lot has changed, all of the

[jira] [Updated] (SPARK-25078) Standalone does not work with spark.authenticate.secret and deploy-mode=cluster

[ https://issues.apache.org/jira/browse/SPARK-25078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imran Rashid updated SPARK-25078: - Summary: Standalone does not work with spark.authenticate.secret and deploy-mode=cluster (was:

[jira] [Commented] (SPARK-25059) Exception while executing an action on DataFrame that read Json

[ https://issues.apache.org/jira/browse/SPARK-25059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575129#comment-16575129 ] Kazuaki Ishizaki commented on SPARK-25059: -- Thank you for reporting the issue. Could you please

[jira] [Comment Edited] (SPARK-25036) Scala 2.12 issues: Compilation error with sbt

[ https://issues.apache.org/jira/browse/SPARK-25036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575137#comment-16575137 ] Kazuaki Ishizaki edited comment on SPARK-25036 at 8/9/18 5:05 PM: --

[jira] [Assigned] (SPARK-25036) Scala 2.12 issues: Compilation error with sbt

[ https://issues.apache.org/jira/browse/SPARK-25036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25036: Assignee: Apache Spark (was: Kazuaki Ishizaki) > Scala 2.12 issues: Compilation error

[jira] [Assigned] (SPARK-25079) [PYTHON] upgrade python 3.4 -> 3.5

[ https://issues.apache.org/jira/browse/SPARK-25079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25079: Assignee: Apache Spark (was: shane knapp) > [PYTHON] upgrade python 3.4 -> 3.5 >

[jira] [Commented] (SPARK-25079) [PYTHON] upgrade python 3.4 -> 3.5

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

[jira] [Assigned] (SPARK-25079) [PYTHON] upgrade python 3.4 -> 3.5

[ https://issues.apache.org/jira/browse/SPARK-25079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25079: Assignee: shane knapp (was: Apache Spark) > [PYTHON] upgrade python 3.4 -> 3.5 >

[jira] [Commented] (SPARK-25079) [PYTHON] upgrade python 3.4 -> 3.5

[ https://issues.apache.org/jira/browse/SPARK-25079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575197#comment-16575197 ] shane knapp commented on SPARK-25079: - SO.  MANY.  MOVING.  PARTS. > [PYTHON] upgrade python 3.4 ->

[jira] [Commented] (SPARK-23207) Shuffle+Repartition on an DataFrame could lead to incorrect answers

[ https://issues.apache.org/jira/browse/SPARK-23207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575097#comment-16575097 ] Imran Rashid commented on SPARK-23207: -- yeah I agree with Tom, silent data loss is a major bug. I

[jira] [Reopened] (SPARK-25036) Scala 2.12 issues: Compilation error with sbt

[ https://issues.apache.org/jira/browse/SPARK-25036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kazuaki Ishizaki reopened SPARK-25036: -- Another type of compilation error is found > Scala 2.12 issues: Compilation error with

[jira] [Assigned] (SPARK-25036) Scala 2.12 issues: Compilation error with sbt

[ https://issues.apache.org/jira/browse/SPARK-25036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25036: Assignee: Kazuaki Ishizaki (was: Apache Spark) > Scala 2.12 issues: Compilation error

[jira] [Created] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

yucai created SPARK-25084: - Summary: "distribute by" on multiple columns may lead to codegen issue Key: SPARK-25084 URL: https://issues.apache.org/jira/browse/SPARK-25084 Project: Spark Issue Type:

[jira] [Commented] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

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

[jira] [Assigned] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

[ https://issues.apache.org/jira/browse/SPARK-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25084: Assignee: (was: Apache Spark) > "distribute by" on multiple columns may lead to

[jira] [Assigned] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

[ https://issues.apache.org/jira/browse/SPARK-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-25084: Assignee: Apache Spark > "distribute by" on multiple columns may lead to codegen issue >

[jira] [Commented] (SPARK-24950) scala DateTimeUtilsSuite daysToMillis and millisToDays fails w/java 8 181-b13

[ https://issues.apache.org/jira/browse/SPARK-24950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575488#comment-16575488 ] Sean Owen commented on SPARK-24950: --- Roger that, will back-port back to 2.1 as best I can. > scala

[jira] [Commented] (SPARK-25079) [PYTHON] upgrade python 3.4 -> 3.5

[ https://issues.apache.org/jira/browse/SPARK-25079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575554#comment-16575554 ] shane knapp commented on SPARK-25079: - i've confirmed, for the master branch at least, that a

[jira] [Updated] (SPARK-25081) Nested spill in ShuffleExternalSorter may access a released memory page

[ https://issues.apache.org/jira/browse/SPARK-25081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated SPARK-25081: - Description: This issue is pretty similar to SPARK-21907. "allocateArray" in

[jira] [Commented] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

[ https://issues.apache.org/jira/browse/SPARK-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575771#comment-16575771 ] Yuming Wang commented on SPARK-25084: - [~smilegator], [~jerryshao] I think It should be target

[jira] [Commented] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

[ https://issues.apache.org/jira/browse/SPARK-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575772#comment-16575772 ] Saisai Shao commented on SPARK-25084: - I'm already preparing new RC4. If this is not a severe issue,

[jira] [Updated] (SPARK-25067) Active tasks exceed total cores of an executor in WebUI

[ https://issues.apache.org/jira/browse/SPARK-25067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] StanZhai updated SPARK-25067: - Attachment: (was: 1533128203469_2.png) > Active tasks exceed total cores of an executor in WebUI >

[jira] [Commented] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

[ https://issues.apache.org/jira/browse/SPARK-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575778#comment-16575778 ] Saisai Shao commented on SPARK-25084: - I see. Unfortunately I've cut the RC4, if it worth to include

[jira] [Commented] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

[ https://issues.apache.org/jira/browse/SPARK-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575774#comment-16575774 ] Saisai Shao commented on SPARK-25084: - Is this a regression or just a bug existed in old version? >

[jira] [Commented] (SPARK-25084) "distribute by" on multiple columns may lead to codegen issue

[ https://issues.apache.org/jira/browse/SPARK-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575777#comment-16575777 ] Yuming Wang commented on SPARK-25084: - It's a regression. > "distribute by" on multiple columns may

  1   2   >