[jira] [Commented] (SPARK-20338) Spaces in spark.eventLog.dir are not correctly handled

[ https://issues.apache.org/jira/browse/SPARK-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976103#comment-15976103 ] zuotingbing commented on SPARK-20338: - Not sure who exactly to ping here, [~jerryshao] could you

[jira] [Commented] (SPARK-20400) Remove References to Third Party Vendors from Spark ASF Documentation

[ https://issues.apache.org/jira/browse/SPARK-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976102#comment-15976102 ] Bill Chambers commented on SPARK-20400: --- I'd like to see what others have to say, maybe this isn't

[jira] [Assigned] (SPARK-20400) Remove References to Third Party Vendors from Spark ASF Documentation

[ https://issues.apache.org/jira/browse/SPARK-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20400: Assignee: (was: Apache Spark) > Remove References to Third Party Vendors from Spark

[jira] [Assigned] (SPARK-20400) Remove References to Third Party Vendors from Spark ASF Documentation

[ https://issues.apache.org/jira/browse/SPARK-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20400: Assignee: Apache Spark > Remove References to Third Party Vendors from Spark ASF

[jira] [Commented] (SPARK-20400) Remove References to Third Party Vendors from Spark ASF Documentation

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

[jira] [Updated] (SPARK-20400) Remove References to Third Party Vendors from Spark ASF Documentation

[ https://issues.apache.org/jira/browse/SPARK-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Chambers updated SPARK-20400: -- Description: Similar to SPARK-17445, vendors should probably not be referenced on the ASF

[jira] [Commented] (SPARK-20081) RandomForestClassifier doesn't seem to support more than 100 labels

[ https://issues.apache.org/jira/browse/SPARK-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976098#comment-15976098 ] Yan Facai (颜发才) commented on SPARK-20081: - By the way, for StringIndexer, numerical label column

[jira] [Created] (SPARK-20400) Remove References to Third Party Vendors from Spark ASF Documentation

Bill Chambers created SPARK-20400: - Summary: Remove References to Third Party Vendors from Spark ASF Documentation Key: SPARK-20400 URL: https://issues.apache.org/jira/browse/SPARK-20400 Project:

[jira] [Updated] (SPARK-20399) Can't use same regex pattern between 1.6 and 2.x due to unescaped sql string in parser

[ https://issues.apache.org/jira/browse/SPARK-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-20399: Description: The new SQL parser is introduced into Spark 2.0. Seems it bring an issue

[jira] [Updated] (SPARK-20399) Can't use same regex pattern between 1.6 and 2.x due to unescaped sql string in parser

[ https://issues.apache.org/jira/browse/SPARK-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-20399: Description: The new SQL parser is introduced into Spark 2.0. Seems it bring an issue

[jira] [Comment Edited] (SPARK-20399) Can't use same regex pattern between 1.6 and 2.x due to unescaped sql string in parser

[ https://issues.apache.org/jira/browse/SPARK-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976047#comment-15976047 ] Liang-Chi Hsieh edited comment on SPARK-20399 at 4/20/17 4:28 AM: -- I

[jira] [Updated] (SPARK-20399) Can't use same regex pattern between 1.6 and 2.x due to unescaped sql string in parser

[ https://issues.apache.org/jira/browse/SPARK-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-20399: Description: The new SQL parser is introduced into Spark 2.0. Seems it bring an issue

[jira] [Commented] (SPARK-20399) Can't use same regex pattern between 1.6 and 2.x due to unescaped sql string in parser

[ https://issues.apache.org/jira/browse/SPARK-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976047#comment-15976047 ] Liang-Chi Hsieh commented on SPARK-20399: - I already have the fix for this. I am not sure if

[jira] [Created] (SPARK-20399) Can't use same regex pattern between 1.6 and 2.x due to unescaped sql string in parser

Liang-Chi Hsieh created SPARK-20399: --- Summary: Can't use same regex pattern between 1.6 and 2.x due to unescaped sql string in parser Key: SPARK-20399 URL: https://issues.apache.org/jira/browse/SPARK-20399

[jira] [Assigned] (SPARK-20375) R wrappers for array and map

[ https://issues.apache.org/jira/browse/SPARK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung reassigned SPARK-20375: Assignee: Maciej Szymkiewicz > R wrappers for array and map >

[jira] [Updated] (SPARK-20375) R wrappers for array and map

[ https://issues.apache.org/jira/browse/SPARK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung updated SPARK-20375: - Affects Version/s: (was: 2.0.0) > R wrappers for array and map >

[jira] [Resolved] (SPARK-20375) R wrappers for array and map

[ https://issues.apache.org/jira/browse/SPARK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung resolved SPARK-20375. -- Resolution: Fixed Fix Version/s: 2.3.0 Target Version/s: 2.3.0 > R wrappers

[jira] [Commented] (SPARK-8971) Support balanced class labels when splitting train/cross validation sets

[ https://issues.apache.org/jira/browse/SPARK-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976027#comment-15976027 ] Tiago Albineli Motta commented on SPARK-8971: - Why not a variation of TrainValidatorSplit to

[jira] [Resolved] (SPARK-20398) range() operator should include cancellation reason when killed

[ https://issues.apache.org/jira/browse/SPARK-20398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin resolved SPARK-20398. - Resolution: Fixed Assignee: Eric Liang Fix Version/s: 2.2.0 > range() operator

[jira] [Resolved] (SPARK-20350) Apply Complementation Laws during boolean expression simplification

[ https://issues.apache.org/jira/browse/SPARK-20350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan resolved SPARK-20350. - Resolution: Fixed Assignee: Michael Styles (was: Wenchen Fan) > Apply Complementation

[jira] [Assigned] (SPARK-20350) Apply Complementation Laws during boolean expression simplification

[ https://issues.apache.org/jira/browse/SPARK-20350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-20350: --- Assignee: Wenchen Fan > Apply Complementation Laws during boolean expression simplification

[jira] [Updated] (SPARK-20350) Apply Complementation Laws during boolean expression simplification

[ https://issues.apache.org/jira/browse/SPARK-20350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan updated SPARK-20350: Fix Version/s: 2.3.0 2.2.0 > Apply Complementation Laws during boolean

[jira] [Assigned] (SPARK-12717) pyspark broadcast fails when using multiple threads

[ https://issues.apache.org/jira/browse/SPARK-12717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-12717: Assignee: Apache Spark > pyspark broadcast fails when using multiple threads >

[jira] [Assigned] (SPARK-12717) pyspark broadcast fails when using multiple threads

[ https://issues.apache.org/jira/browse/SPARK-12717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-12717: Assignee: (was: Apache Spark) > pyspark broadcast fails when using multiple threads >

[jira] [Commented] (SPARK-12717) pyspark broadcast fails when using multiple threads

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

[jira] [Assigned] (SPARK-20314) Inconsistent error handling in JSON parsing SQL functions

[ https://issues.apache.org/jira/browse/SPARK-20314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20314: Assignee: (was: Apache Spark) > Inconsistent error handling in JSON parsing SQL

[jira] [Assigned] (SPARK-20314) Inconsistent error handling in JSON parsing SQL functions

[ https://issues.apache.org/jira/browse/SPARK-20314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20314: Assignee: Apache Spark > Inconsistent error handling in JSON parsing SQL functions >

[jira] [Commented] (SPARK-20314) Inconsistent error handling in JSON parsing SQL functions

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

[jira] [Resolved] (SPARK-20297) Parquet Decimal(12,2) written by Spark is unreadable by Hive and Impala

[ https://issues.apache.org/jira/browse/SPARK-20297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon resolved SPARK-20297. -- Resolution: Not A Problem > Parquet Decimal(12,2) written by Spark is unreadable by Hive and

[jira] [Commented] (SPARK-20297) Parquet Decimal(12,2) written by Spark is unreadable by Hive and Impala

[ https://issues.apache.org/jira/browse/SPARK-20297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975763#comment-15975763 ] Hyukjin Kwon commented on SPARK-20297: -- Yea, then it looks both ways are still vaild whether it is

[jira] [Commented] (SPARK-20314) Inconsistent error handling in JSON parsing SQL functions

[ https://issues.apache.org/jira/browse/SPARK-20314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975744#comment-15975744 ] Eric Wasserman commented on SPARK-20314: h2. Cause The cause of the error appears to be a misuse

[jira] [Reopened] (SPARK-16548) java.io.CharConversionException: Invalid UTF-32 character prevents me from querying my data

[ https://issues.apache.org/jira/browse/SPARK-16548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust reopened SPARK-16548: -- I'm not sure I agree. The default behavior for parsing corrupted JSON is to return

[jira] [Assigned] (SPARK-20398) range() operator should include cancellation reason when killed

[ https://issues.apache.org/jira/browse/SPARK-20398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20398: Assignee: Apache Spark > range() operator should include cancellation reason when killed

[jira] [Assigned] (SPARK-20398) range() operator should include cancellation reason when killed

[ https://issues.apache.org/jira/browse/SPARK-20398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20398: Assignee: (was: Apache Spark) > range() operator should include cancellation reason

[jira] [Created] (SPARK-20398) range() operator should include cancellation reason when killed

Eric Liang created SPARK-20398: -- Summary: range() operator should include cancellation reason when killed Key: SPARK-20398 URL: https://issues.apache.org/jira/browse/SPARK-20398 Project: Spark

[jira] [Commented] (SPARK-20398) range() operator should include cancellation reason when killed

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

[jira] [Closed] (SPARK-20390) Non-deterministic expressions could exist in grouping keys

[ https://issues.apache.org/jira/browse/SPARK-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takeshi Yamamuro closed SPARK-20390. Resolution: Not A Problem > Non-deterministic expressions could exist in grouping keys >

[jira] [Commented] (SPARK-20314) Inconsistent error handling in JSON parsing SQL functions

[ https://issues.apache.org/jira/browse/SPARK-20314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975692#comment-15975692 ] Eric Wasserman commented on SPARK-20314: {code:title=JsonParseError.scala|borderStyle=solid} //

[jira] [Commented] (SPARK-20395) Upgrade to Scala 2.11.11

[ https://issues.apache.org/jira/browse/SPARK-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975637#comment-15975637 ] Jeremy Smith commented on SPARK-20395: -- [~srowen] genjavadoc version tracks the complete Scala

[jira] [Commented] (SPARK-20297) Parquet Decimal(12,2) written by Spark is unreadable by Hive and Impala

[ https://issues.apache.org/jira/browse/SPARK-20297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975559#comment-15975559 ] Tim Armstrong commented on SPARK-20297: --- The standard doesn't say that smaller decimals *have* to

[jira] [Comment Edited] (SPARK-16599) java.util.NoSuchElementException: None.get at at org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(BlockInfoManager.scala:343)

[ https://issues.apache.org/jira/browse/SPARK-16599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975490#comment-15975490 ] ilker ozsaracoglu edited comment on SPARK-16599 at 4/19/17 8:52 PM:

[jira] [Commented] (SPARK-19547) KafkaUtil throw 'No current assignment for partition' Exception

[ https://issues.apache.org/jira/browse/SPARK-19547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975500#comment-15975500 ] Rajkumar More commented on SPARK-19547: --- HI, What was the resolution to this issue ? Thanks, Raj

[jira] [Comment Edited] (SPARK-16599) java.util.NoSuchElementException: None.get at at org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(BlockInfoManager.scala:343)

[ https://issues.apache.org/jira/browse/SPARK-16599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975490#comment-15975490 ] ilker ozsaracoglu edited comment on SPARK-16599 at 4/19/17 8:50 PM:

[jira] [Commented] (SPARK-16599) java.util.NoSuchElementException: None.get at at org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(BlockInfoManager.scala:343)

[ https://issues.apache.org/jira/browse/SPARK-16599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975490#comment-15975490 ] ilker ozsaracoglu commented on SPARK-16599: --- [~sowen], I get this error consistently. I am

[jira] [Commented] (SPARK-20395) Upgrade to Scala 2.11.11

[ https://issues.apache.org/jira/browse/SPARK-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975485#comment-15975485 ] Sean Owen commented on SPARK-20395: --- ... and a new genjavadoc release too? really, why does that block?

[jira] [Commented] (SPARK-20395) Upgrade to Scala 2.11.11

[ https://issues.apache.org/jira/browse/SPARK-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975458#comment-15975458 ] Jeremy Smith commented on SPARK-20395: -- Depends on

[jira] [Resolved] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

[ https://issues.apache.org/jira/browse/SPARK-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu resolved SPARK-20397. -- Resolution: Fixed Fix Version/s: 2.2.0 > Flaky Test: test_streaming.R.Terminated by

[jira] [Assigned] (SPARK-20378) StreamSinkProvider should provide schema in createSink.

[ https://issues.apache.org/jira/browse/SPARK-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20378: Assignee: Apache Spark > StreamSinkProvider should provide schema in createSink. >

[jira] [Assigned] (SPARK-20378) StreamSinkProvider should provide schema in createSink.

[ https://issues.apache.org/jira/browse/SPARK-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20378: Assignee: (was: Apache Spark) > StreamSinkProvider should provide schema in

[jira] [Commented] (SPARK-20378) StreamSinkProvider should provide schema in createSink.

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

[jira] [Commented] (SPARK-16845) org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificOrdering" grows beyond 64 KB

[ https://issues.apache.org/jira/browse/SPARK-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975386#comment-15975386 ] Ethan Xu commented on SPARK-16845: -- Thanks [~kiszk] ! I'm following that PR. I'm surprised that 3000

[jira] [Commented] (SPARK-19732) DataFrame.fillna() does not work for bools in PySpark

[ https://issues.apache.org/jira/browse/SPARK-19732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975369#comment-15975369 ] Srinivasa Reddy Vundela commented on SPARK-19732: - Hi [~lenfro], I was checking the

[jira] [Reopened] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust reopened SPARK-18891: -- > Support for specific collection types > - > >

[jira] [Resolved] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust resolved SPARK-18891. -- Resolution: Fixed Fix Version/s: 2.2.0 > Support for specific collection types

[jira] [Commented] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

[ https://issues.apache.org/jira/browse/SPARK-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975269#comment-15975269 ] Shixiong Zhu commented on SPARK-20397: -- I saw the other tests use 5 sec and so just to make it

[jira] [Commented] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

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

[jira] [Assigned] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

[ https://issues.apache.org/jira/browse/SPARK-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20397: Assignee: Shixiong Zhu (was: Apache Spark) > Flaky Test: test_streaming.R.Terminated by

[jira] [Assigned] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

[ https://issues.apache.org/jira/browse/SPARK-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20397: Assignee: Apache Spark (was: Shixiong Zhu) > Flaky Test: test_streaming.R.Terminated by

[jira] [Commented] (SPARK-16845) org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificOrdering" grows beyond 64 KB

[ https://issues.apache.org/jira/browse/SPARK-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975194#comment-15975194 ] Kazuaki Ishizaki commented on SPARK-16845: -- You are seeing another exception. While [This

[jira] [Comment Edited] (SPARK-16845) org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificOrdering" grows beyond 64 KB

[ https://issues.apache.org/jira/browse/SPARK-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975194#comment-15975194 ] Kazuaki Ishizaki edited comment on SPARK-16845 at 4/19/17 6:05 PM: --- You

[jira] [Assigned] (SPARK-20036) impossible to read a whole kafka topic using kafka 0.10 and spark 2.0.0

[ https://issues.apache.org/jira/browse/SPARK-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen reassigned SPARK-20036: - Assignee: Cody Koeninger Priority: Minor (was: Major) Component/s: (was:

[jira] [Resolved] (SPARK-20036) impossible to read a whole kafka topic using kafka 0.10 and spark 2.0.0

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

[jira] [Comment Edited] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

[ https://issues.apache.org/jira/browse/SPARK-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975170#comment-15975170 ] Felix Cheung edited comment on SPARK-20397 at 4/19/17 5:56 PM: --- I'm fine if

[jira] [Commented] (SPARK-16845) org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificOrdering" grows beyond 64 KB

[ https://issues.apache.org/jira/browse/SPARK-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975171#comment-15975171 ] Ethan Xu commented on SPARK-16845: -- [~lwlin] I encountered the same error when handling a data frame

[jira] [Commented] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

[ https://issues.apache.org/jira/browse/SPARK-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975170#comment-15975170 ] Felix Cheung commented on SPARK-20397: -- I'm fine if we want to increase the time out - > Flaky

[jira] [Updated] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

[ https://issues.apache.org/jira/browse/SPARK-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated SPARK-20397: - Labels: flaky-test (was: ) > Flaky Test: test_streaming.R.Terminated by error >

[jira] [Created] (SPARK-20397) Flaky Test: test_streaming.R.Terminated by error

Shixiong Zhu created SPARK-20397: Summary: Flaky Test: test_streaming.R.Terminated by error Key: SPARK-20397 URL: https://issues.apache.org/jira/browse/SPARK-20397 Project: Spark Issue Type:

[jira] [Created] (SPARK-20396) Add support for pandas udf in pyspark

Li Jin created SPARK-20396: -- Summary: Add support for pandas udf in pyspark Key: SPARK-20396 URL: https://issues.apache.org/jira/browse/SPARK-20396 Project: Spark Issue Type: New Feature

[jira] [Commented] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975115#comment-15975115 ] Thomas Graves commented on SPARK-20391: --- > My proposal was to add 2 extra fields which duplicate

[jira] [Resolved] (SPARK-20081) RandomForestClassifier doesn't seem to support more than 100 labels

[ https://issues.apache.org/jira/browse/SPARK-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph K. Bradley resolved SPARK-20081. --- Resolution: Not A Problem > RandomForestClassifier doesn't seem to support more than

[jira] [Commented] (SPARK-20081) RandomForestClassifier doesn't seem to support more than 100 labels

[ https://issues.apache.org/jira/browse/SPARK-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975091#comment-15975091 ] Joseph K. Bradley commented on SPARK-20081: --- StringIndexer does indeed set the number of

[jira] [Updated] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imran Rashid updated SPARK-20391: - Priority: Blocker (was: Minor) > Properly rename the memory related fields in ExecutorSummary

[jira] [Commented] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975062#comment-15975062 ] Imran Rashid commented on SPARK-20391: -- bq. If we want to change the names of the other 2 we could

[jira] [Commented] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975029#comment-15975029 ] Thomas Graves commented on SPARK-20391: --- I agree that if its been released we can't change it, the

[jira] [Commented] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974969#comment-15974969 ] Takeshi Yamamuro commented on SPARK-18891: -- I also checked `Vector` and `IndexedSeq` work. >

[jira] [Updated] (SPARK-20395) Upgrade to Scala 2.11.11

[ https://issues.apache.org/jira/browse/SPARK-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-20395: -- Priority: Minor (was: Major) Agree, I think you can open a PR. > Upgrade to Scala 2.11.11 >

[jira] [Comment Edited] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974924#comment-15974924 ] Imran Rashid edited comment on SPARK-20391 at 4/19/17 3:42 PM: ---

[jira] [Commented] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974926#comment-15974926 ] Imran Rashid commented on SPARK-20391: -- cc [~tgraves] [~jsoltren] > Properly rename the memory

[jira] [Commented] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974924#comment-15974924 ] Imran Rashid commented on SPARK-20391: -- {{memoryUsed}} and {{maxMemory}} exist in already released

[jira] [Comment Edited] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974841#comment-15974841 ] Kazuaki Ishizaki edited comment on SPARK-18891 at 4/19/17 3:08 PM: --- I

[jira] [Comment Edited] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974841#comment-15974841 ] Kazuaki Ishizaki edited comment on SPARK-18891 at 4/19/17 3:08 PM: --- I

[jira] [Comment Edited] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974841#comment-15974841 ] Kazuaki Ishizaki edited comment on SPARK-18891 at 4/19/17 3:07 PM: --- I

[jira] [Created] (SPARK-20395) Upgrade to Scala 2.11.11

Jeremy Smith created SPARK-20395: Summary: Upgrade to Scala 2.11.11 Key: SPARK-20395 URL: https://issues.apache.org/jira/browse/SPARK-20395 Project: Spark Issue Type: Dependency upgrade

[jira] [Created] (SPARK-20394) Replication factor value Not changing properly

Kannan Subramanian created SPARK-20394: -- Summary: Replication factor value Not changing properly Key: SPARK-20394 URL: https://issues.apache.org/jira/browse/SPARK-20394 Project: Spark

[jira] [Comment Edited] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974841#comment-15974841 ] Kazuaki Ishizaki edited comment on SPARK-18891 at 4/19/17 3:00 PM: --- I

[jira] [Commented] (SPARK-18891) Support for specific collection types

[ https://issues.apache.org/jira/browse/SPARK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974841#comment-15974841 ] Kazuaki Ishizaki commented on SPARK-18891: -- I confirmed that that the latest master branch works

[jira] [Assigned] (SPARK-20393) Strengthen Spark to prevent XSS vulnerabilities

[ https://issues.apache.org/jira/browse/SPARK-20393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20393: Assignee: (was: Apache Spark) > Strengthen Spark to prevent XSS vulnerabilities >

[jira] [Assigned] (SPARK-20393) Strengthen Spark to prevent XSS vulnerabilities

[ https://issues.apache.org/jira/browse/SPARK-20393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20393: Assignee: Apache Spark > Strengthen Spark to prevent XSS vulnerabilities >

[jira] [Issue Comment Deleted] (SPARK-20343) SBT master build for Hadoop 2.6 in Jenkins fails due to Avro version resolution

[ https://issues.apache.org/jira/browse/SPARK-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-20343: -- Comment: was deleted (was: Issue resolved by pull request 17642

[jira] [Commented] (SPARK-20343) SBT master build for Hadoop 2.6 in Jenkins fails due to Avro version resolution

[ https://issues.apache.org/jira/browse/SPARK-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974789#comment-15974789 ] Sean Owen commented on SPARK-20343: --- Resolved by https://github.com/apache/spark/pull/17669 > SBT

[jira] [Commented] (SPARK-20393) Strengthen Spark to prevent XSS vulnerabilities

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

[jira] [Created] (SPARK-20393) Strengthen Spark to prevent XSS vulnerabilities

Nicholas Marion created SPARK-20393: --- Summary: Strengthen Spark to prevent XSS vulnerabilities Key: SPARK-20393 URL: https://issues.apache.org/jira/browse/SPARK-20393 Project: Spark Issue

[jira] [Updated] (SPARK-20392) Slow performance when calling fit on ML pipeline for dataset with many columns but few rows

[ https://issues.apache.org/jira/browse/SPARK-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Becker updated SPARK-20392: - Attachment: giant_query_plan_for_fitting_pipeline.txt Giant nested query plan using when calling

[jira] [Commented] (SPARK-18492) GeneratedIterator grows beyond 64 KB

[ https://issues.apache.org/jira/browse/SPARK-18492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974766#comment-15974766 ] Kazuaki Ishizaki commented on SPARK-18492: -- Do you see the same problem with the latest master

[jira] [Updated] (SPARK-20392) Slow performance when calling fit on ML pipeline for dataset with many columns but few rows

[ https://issues.apache.org/jira/browse/SPARK-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Becker updated SPARK-20392: - Attachment: blockbuster.csv Attaching blockbuster.csv data file with many columns, but few rows.

[jira] [Created] (SPARK-20392) Slow performance when calling fit on ML pipeline for dataset with many columns but few rows

Barry Becker created SPARK-20392: Summary: Slow performance when calling fit on ML pipeline for dataset with many columns but few rows Key: SPARK-20392 URL: https://issues.apache.org/jira/browse/SPARK-20392

[jira] [Updated] (SPARK-20389) Upgrade kryo to fix NegativeArraySizeException

[ https://issues.apache.org/jira/browse/SPARK-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Heiler updated SPARK-20389: - Indeed kryo 4. > Upgrade kryo to fix NegativeArraySizeException >

[jira] [Commented] (SPARK-20341) Support BigIngeger values > 19 precision

[ https://issues.apache.org/jira/browse/SPARK-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974698#comment-15974698 ] Paul Zaczkieiwcz commented on SPARK-20341: -- Thanks! I saw {{scala.math.BigInt}} and

[jira] [Commented] (SPARK-20391) Properly rename the memory related fields in ExecutorSummary REST API

[ https://issues.apache.org/jira/browse/SPARK-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974685#comment-15974685 ] Saisai Shao commented on SPARK-20391: - [~irashid], would be grateful to hear your suggestion. >

[jira] [Commented] (SPARK-20184) performance regression for complex/long sql when enable whole stage codegen

[ https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974682#comment-15974682 ] Kazuaki Ishizaki commented on SPARK-20184: -- I succeeded to reproduce this... {code} % git log |

  1   2   >