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

[ https://issues.apache.org/jira/browse/SPARK-23874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426484#comment-16426484 ] Xiao Li commented on SPARK-23874: - [~bryanc] [~hyukjin.kwon] [~icexelloss] Could any of you help this

[jira] [Created] (SPARK-23874) Upgrade apache/arrow to 0.9.0

Xiao Li created SPARK-23874: --- Summary: Upgrade apache/arrow to 0.9.0 Key: SPARK-23874 URL: https://issues.apache.org/jira/browse/SPARK-23874 Project: Spark Issue Type: Improvement

[jira] [Updated] (SPARK-23815) Spark writer dynamic partition overwrite mode fails to write output on multi level partition

[ https://issues.apache.org/jira/browse/SPARK-23815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fangshi Li updated SPARK-23815: --- Description: Spark introduced new writer mode to overwrite only related partitions in SPARK-20236.

[jira] [Assigned] (SPARK-23873) Use accessors in interpreted LambdaVariable

[ https://issues.apache.org/jira/browse/SPARK-23873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23873: Assignee: Apache Spark > Use accessors in interpreted LambdaVariable >

[jira] [Assigned] (SPARK-23873) Use accessors in interpreted LambdaVariable

[ https://issues.apache.org/jira/browse/SPARK-23873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23873: Assignee: (was: Apache Spark) > Use accessors in interpreted LambdaVariable >

[jira] [Commented] (SPARK-23873) Use accessors in interpreted LambdaVariable

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

[jira] [Commented] (SPARK-23589) Add interpreted execution for ExternalMapToCatalyst expression

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

[jira] [Assigned] (SPARK-23589) Add interpreted execution for ExternalMapToCatalyst expression

[ https://issues.apache.org/jira/browse/SPARK-23589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23589: Assignee: (was: Apache Spark) > Add interpreted execution for ExternalMapToCatalyst

[jira] [Assigned] (SPARK-23589) Add interpreted execution for ExternalMapToCatalyst expression

[ https://issues.apache.org/jira/browse/SPARK-23589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23589: Assignee: Apache Spark > Add interpreted execution for ExternalMapToCatalyst expression >

[jira] [Assigned] (SPARK-23588) Add interpreted execution for CatalystToExternalMap expression

[ https://issues.apache.org/jira/browse/SPARK-23588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23588: Assignee: Apache Spark (was: Takeshi Yamamuro) > Add interpreted execution for

[jira] [Assigned] (SPARK-23588) Add interpreted execution for CatalystToExternalMap expression

[ https://issues.apache.org/jira/browse/SPARK-23588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23588: Assignee: Takeshi Yamamuro (was: Apache Spark) > Add interpreted execution for

[jira] [Commented] (SPARK-23588) Add interpreted execution for CatalystToExternalMap expression

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

[jira] [Created] (SPARK-23873) Use accessors in interpreted LambdaVariable

Liang-Chi Hsieh created SPARK-23873: --- Summary: Use accessors in interpreted LambdaVariable Key: SPARK-23873 URL: https://issues.apache.org/jira/browse/SPARK-23873 Project: Spark Issue

[jira] [Resolved] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla resolved SPARK-23869. - Resolution: Invalid > Spark 2.3.0 left outer join not emitting null

[jira] [Issue Comment Deleted] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla updated SPARK-23869: Comment: was deleted (was: Hey,  Any luck on this? Am I missing

[jira] [Updated] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla updated SPARK-23869: Issue Type: Bug (was: Test) > Spark 2.3.0 left outer join not emitting

[jira] [Updated] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla updated SPARK-23869: Description: Left outer join on two streams not emitting the null outputs.

[jira] [Commented] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426417#comment-16426417 ] bharath kumar avusherla commented on SPARK-23869: - Hey,  Any luck on this? Am I missing

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Updated] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

[ https://issues.apache.org/jira/browse/SPARK-23872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Park Chan Min updated SPARK-23872: -- Description: In Spark 2.1.0, two sessions worked normally In 2.3.0, the first session

[jira] [Created] (SPARK-23872) You can not connect to another metastore uri using two Spark sessions

Park Chan Min created SPARK-23872: - Summary: You can not connect to another metastore uri using two Spark sessions Key: SPARK-23872 URL: https://issues.apache.org/jira/browse/SPARK-23872 Project:

[jira] [Commented] (SPARK-19842) Informational Referential Integrity Constraints Support in Spark

[ https://issues.apache.org/jira/browse/SPARK-19842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426369#comment-16426369 ] Takeshi Yamamuro commented on SPARK-19842: -- Sorry, my bad. I just suggested we might need a

[jira] [Comment Edited] (SPARK-19842) Informational Referential Integrity Constraints Support in Spark

[ https://issues.apache.org/jira/browse/SPARK-19842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422041#comment-16422041 ] Takeshi Yamamuro edited comment on SPARK-19842 at 4/5/18 12:29 AM: ---

[jira] [Assigned] (SPARK-23870) Forward RFormula handleInvalid Param to VectorAssembler

[ https://issues.apache.org/jira/browse/SPARK-23870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23870: Assignee: Apache Spark > Forward RFormula handleInvalid Param to VectorAssembler >

[jira] [Resolved] (SPARK-23637) Yarn might allocate more resource if a same executor is killed multiple times.

[ https://issues.apache.org/jira/browse/SPARK-23637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin resolved SPARK-23637. Resolution: Fixed Fix Version/s: 2.3.1 2.4.0 Issue resolved by

[jira] [Commented] (SPARK-23870) Forward RFormula handleInvalid Param to VectorAssembler

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

[jira] [Assigned] (SPARK-23870) Forward RFormula handleInvalid Param to VectorAssembler

[ https://issues.apache.org/jira/browse/SPARK-23870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23870: Assignee: (was: Apache Spark) > Forward RFormula handleInvalid Param to

[jira] [Assigned] (SPARK-23637) Yarn might allocate more resource if a same executor is killed multiple times.

[ https://issues.apache.org/jira/browse/SPARK-23637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin reassigned SPARK-23637: -- Assignee: jin xing > Yarn might allocate more resource if a same executor is killed

[jira] [Created] (SPARK-23871) add python api for VectorAssembler handleInvalid

yogesh garg created SPARK-23871: --- Summary: add python api for VectorAssembler handleInvalid Key: SPARK-23871 URL: https://issues.apache.org/jira/browse/SPARK-23871 Project: Spark Issue Type:

[jira] [Created] (SPARK-23870) Forward RFormula handleInvalid Param to VectorAssembler

yogesh garg created SPARK-23870: --- Summary: Forward RFormula handleInvalid Param to VectorAssembler Key: SPARK-23870 URL: https://issues.apache.org/jira/browse/SPARK-23870 Project: Spark Issue

[jira] [Assigned] (SPARK-23838) SparkUI: Running SQL query displayed as "completed" in SQL tab

[ https://issues.apache.org/jira/browse/SPARK-23838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin reassigned SPARK-23838: -- Assignee: Gengliang Wang > SparkUI: Running SQL query displayed as "completed" in SQL

[jira] [Resolved] (SPARK-23838) SparkUI: Running SQL query displayed as "completed" in SQL tab

[ https://issues.apache.org/jira/browse/SPARK-23838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin resolved SPARK-23838. Resolution: Fixed Fix Version/s: 2.3.1 2.4.0 Issue resolved by

[jira] [Commented] (SPARK-23094) Json Readers choose wrong encoding when bad records are present and fail

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

[jira] [Resolved] (SPARK-23668) Support for imagePullSecrets k8s option

[ https://issues.apache.org/jira/browse/SPARK-23668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anirudh Ramanathan resolved SPARK-23668. Resolution: Fixed > Support for imagePullSecrets k8s option >

[jira] [Resolved] (SPARK-23567) spark.redaction.regex should not include user by default, docs not updated

[ https://issues.apache.org/jira/browse/SPARK-23567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves resolved SPARK-23567. --- Resolution: Duplicate > spark.redaction.regex should not include user by default, docs not

[jira] [Updated] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla updated SPARK-23869: Description: Left outer join on two streams not emitting the null outputs.

[jira] [Updated] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla updated SPARK-23869: Issue Type: Test (was: Bug) > Spark 2.3.0 left outer join not emitting

[jira] [Updated] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla updated SPARK-23869: Priority: Major (was: Blocker) > Spark 2.3.0 left outer join not emitting

[jira] [Updated] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

[ https://issues.apache.org/jira/browse/SPARK-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath kumar avusherla updated SPARK-23869: Description: Left outer join on two streams not emitting the null outputs.

[jira] [Created] (SPARK-23869) Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream

bharath kumar avusherla created SPARK-23869: --- Summary: Spark 2.3.0 left outer join not emitting null values instead waiting for the record in other stream Key: SPARK-23869 URL:

[jira] [Updated] (SPARK-23615) Add maxDF Parameter to Python CountVectorizer

[ https://issues.apache.org/jira/browse/SPARK-23615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-23615: Issue Type: Sub-task (was: Improvement) Parent: SPARK-23483 > Add maxDF Parameter to Python

[jira] [Updated] (SPARK-23084) Add unboundedPreceding(), unboundedFollowing() and currentRow() to PySpark

[ https://issues.apache.org/jira/browse/SPARK-23084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-23084: Issue Type: Sub-task (was: Improvement) Parent: SPARK-23483 > Add unboundedPreceding(),

[jira] [Updated] (SPARK-23344) Add KMeans distanceMeasure param to PySpark

[ https://issues.apache.org/jira/browse/SPARK-23344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-23344: Issue Type: Sub-task (was: Improvement) Parent: SPARK-23483 > Add KMeans distanceMeasure param to

[jira] [Updated] (SPARK-22624) Expose range partitioning shuffle introduced by SPARK-22614

[ https://issues.apache.org/jira/browse/SPARK-22624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-22624: Issue Type: Sub-task (was: Improvement) Parent: SPARK-23483 > Expose range partitioning shuffle

[jira] [Resolved] (SPARK-23868) Fix scala.MatchError in literals.sql.out

[ https://issues.apache.org/jira/browse/SPARK-23868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li resolved SPARK-23868. - Resolution: Fixed Assignee: Takeshi Yamamuro Fix Version/s: 2.4.0

[jira] [Created] (SPARK-23868) Fix scala.MatchError in literals.sql.out

Xiao Li created SPARK-23868: --- Summary: Fix scala.MatchError in literals.sql.out Key: SPARK-23868 URL: https://issues.apache.org/jira/browse/SPARK-23868 Project: Spark Issue Type: Bug

[jira] [Reopened] (SPARK-23264) Support interval values without INTERVAL clauses

[ https://issues.apache.org/jira/browse/SPARK-23264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li reopened SPARK-23264: - > Support interval values without INTERVAL clauses > > >

[jira] [Updated] (SPARK-23614) Union produces incorrect results when caching is used

[ https://issues.apache.org/jira/browse/SPARK-23614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-23614: Labels: correctness (was: ) > Union produces incorrect results when caching is used >

[jira] [Commented] (SPARK-19842) Informational Referential Integrity Constraints Support in Spark

[ https://issues.apache.org/jira/browse/SPARK-19842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425845#comment-16425845 ] Ioana Delaney commented on SPARK-19842: --- [~maropu] Thank you for reviewing the document. From your

[jira] [Assigned] (SPARK-23614) Union produces incorrect results when caching is used

[ https://issues.apache.org/jira/browse/SPARK-23614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li reassigned SPARK-23614: --- Assignee: Liang-Chi Hsieh > Union produces incorrect results when caching is used >

[jira] [Commented] (SPARK-21255) NPE when creating encoder for enum

[ https://issues.apache.org/jira/browse/SPARK-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425832#comment-16425832 ] Fangshi Li commented on SPARK-21255: created a follow up issue to add the java enum support in scala

[jira] [Comment Edited] (SPARK-21255) NPE when creating encoder for enum

[ https://issues.apache.org/jira/browse/SPARK-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425832#comment-16425832 ] Fangshi Li edited comment on SPARK-21255 at 4/4/18 4:44 PM: created a follow

[jira] [Resolved] (SPARK-23583) Add interpreted execution to Invoke expression

[ https://issues.apache.org/jira/browse/SPARK-23583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herman van Hovell resolved SPARK-23583. --- Resolution: Fixed Assignee: Kazuaki Ishizaki Fix Version/s: 2.4.0 >

[jira] [Assigned] (SPARK-23861) Clarify behavior of default window frame boundaries with and without orderBy clause

[ https://issues.apache.org/jira/browse/SPARK-23861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23861: Assignee: (was: Apache Spark) > Clarify behavior of default window frame boundaries

[jira] [Commented] (SPARK-23861) Clarify behavior of default window frame boundaries with and without orderBy clause

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

[jira] [Assigned] (SPARK-23861) Clarify behavior of default window frame boundaries with and without orderBy clause

[ https://issues.apache.org/jira/browse/SPARK-23861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23861: Assignee: Apache Spark > Clarify behavior of default window frame boundaries with and

[jira] [Assigned] (SPARK-23867) com.codahale.metrics.Counter output in log message has no toString method

[ https://issues.apache.org/jira/browse/SPARK-23867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23867: Assignee: Apache Spark > com.codahale.metrics.Counter output in log message has no

[jira] [Assigned] (SPARK-23867) com.codahale.metrics.Counter output in log message has no toString method

[ https://issues.apache.org/jira/browse/SPARK-23867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23867: Assignee: (was: Apache Spark) > com.codahale.metrics.Counter output in log message

[jira] [Commented] (SPARK-23867) com.codahale.metrics.Counter output in log message has no toString method

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

[jira] [Assigned] (SPARK-23835) When Dataset.as converts column from nullable to non-nullable type, null Doubles are converted silently to -1

[ https://issues.apache.org/jira/browse/SPARK-23835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23835: Assignee: (was: Apache Spark) > When Dataset.as converts column from nullable to

[jira] [Commented] (SPARK-23835) When Dataset.as converts column from nullable to non-nullable type, null Doubles are converted silently to -1

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

[jira] [Assigned] (SPARK-23835) When Dataset.as converts column from nullable to non-nullable type, null Doubles are converted silently to -1

[ https://issues.apache.org/jira/browse/SPARK-23835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23835: Assignee: Apache Spark > When Dataset.as converts column from nullable to non-nullable

[jira] [Commented] (SPARK-23867) com.codahale.metrics.Counter output in log message has no toString method

[ https://issues.apache.org/jira/browse/SPARK-23867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425680#comment-16425680 ] Patrick Pisciuneri commented on SPARK-23867: Here is the relevant part of the code:

[jira] [Created] (SPARK-23867) com.codahale.metrics.Counter output in log message has no toString method

Patrick Pisciuneri created SPARK-23867: -- Summary: com.codahale.metrics.Counter output in log message has no toString method Key: SPARK-23867 URL: https://issues.apache.org/jira/browse/SPARK-23867

[jira] [Created] (SPARK-23866) Extend ALTER TABLE DROP PARTITION syntax to use all comparators

Dong Jiang created SPARK-23866: -- Summary: Extend ALTER TABLE DROP PARTITION syntax to use all comparators Key: SPARK-23866 URL: https://issues.apache.org/jira/browse/SPARK-23866 Project: Spark

[jira] [Resolved] (SPARK-22769) When driver stopping, there is errors: "Could not find CoarseGrainedScheduler" and "RpcEnv already stopped"

[ https://issues.apache.org/jira/browse/SPARK-22769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-22769. --- Resolution: Won't Fix > When driver stopping, there is errors: "Could not find >

[jira] [Updated] (SPARK-23865) Not able to load file from Spark Dataframes

[ https://issues.apache.org/jira/browse/SPARK-23865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith updated SPARK-23865: Description: Hello, I am in the phase of learning Spark as part of it trying examples. I am using the

[jira] [Created] (SPARK-23865) Not able to load file from Spark Dataframes

Renjith created SPARK-23865: --- Summary: Not able to load file from Spark Dataframes Key: SPARK-23865 URL: https://issues.apache.org/jira/browse/SPARK-23865 Project: Spark Issue Type: Bug

[jira] [Comment Edited] (SPARK-23856) Spark jdbc setQueryTimeout option

[ https://issues.apache.org/jira/browse/SPARK-23856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423907#comment-16423907 ] Dmitry Mikhailov edited comment on SPARK-23856 at 4/4/18 9:05 AM: -- Yes,

[jira] [Commented] (SPARK-23285) Allow spark.executor.cores to be fractional

[ https://issues.apache.org/jira/browse/SPARK-23285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425206#comment-16425206 ] Felix Cheung commented on SPARK-23285: -- fixed in 2.3, updating. > Allow spark.executor.cores to be

[jira] [Updated] (SPARK-23285) Allow spark.executor.cores to be fractional

[ https://issues.apache.org/jira/browse/SPARK-23285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung updated SPARK-23285: - Fix Version/s: 2.4.0 > Allow spark.executor.cores to be fractional >

[jira] [Comment Edited] (SPARK-23285) Allow spark.executor.cores to be fractional

[ https://issues.apache.org/jira/browse/SPARK-23285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425206#comment-16425206 ] Felix Cheung edited comment on SPARK-23285 at 4/4/18 8:53 AM: -- fixed in 2.4,

[jira] [Commented] (SPARK-23680) entrypoint.sh does not accept arbitrary UIDs, returning as an error

[ https://issues.apache.org/jira/browse/SPARK-23680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425202#comment-16425202 ] Felix Cheung commented on SPARK-23680: -- also, please check fixed version and target version when

[jira] [Updated] (SPARK-23680) entrypoint.sh does not accept arbitrary UIDs, returning as an error

[ https://issues.apache.org/jira/browse/SPARK-23680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung updated SPARK-23680: - Target Version/s: 2.4.0 (was: 2.3.1, 2.4.0) > entrypoint.sh does not accept arbitrary UIDs,

[jira] [Updated] (SPARK-23680) entrypoint.sh does not accept arbitrary UIDs, returning as an error

[ https://issues.apache.org/jira/browse/SPARK-23680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung updated SPARK-23680: - Fix Version/s: 2.4.0 > entrypoint.sh does not accept arbitrary UIDs, returning as an error >

[jira] [Assigned] (SPARK-23680) entrypoint.sh does not accept arbitrary UIDs, returning as an error

[ https://issues.apache.org/jira/browse/SPARK-23680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung reassigned SPARK-23680: Assignee: Ricardo Martinelli de Oliveira > entrypoint.sh does not accept arbitrary UIDs,

[jira] [Commented] (SPARK-23680) entrypoint.sh does not accept arbitrary UIDs, returning as an error

[ https://issues.apache.org/jira/browse/SPARK-23680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425200#comment-16425200 ] Felix Cheung commented on SPARK-23680: -- try now. i also had to add rmartine - seemed like this was

[jira] [Created] (SPARK-23864) Add Unsafe* copy methods to UnsafeWriter

Herman van Hovell created SPARK-23864: - Summary: Add Unsafe* copy methods to UnsafeWriter Key: SPARK-23864 URL: https://issues.apache.org/jira/browse/SPARK-23864 Project: Spark Issue

[jira] [Updated] (SPARK-23863) Wholetext mode should not add line breaks

[ https://issues.apache.org/jira/browse/SPARK-23863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chencheng updated SPARK-23863: -- Description: We merged multiple files in the Text format. When using the select count(1) to count the

[jira] [Assigned] (SPARK-23863) Wholetext mode should not add line breaks

[ https://issues.apache.org/jira/browse/SPARK-23863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23863: Assignee: (was: Apache Spark) > Wholetext mode should not add line breaks >

[jira] [Assigned] (SPARK-23863) Wholetext mode should not add line breaks

[ https://issues.apache.org/jira/browse/SPARK-23863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-23863: Assignee: Apache Spark > Wholetext mode should not add line breaks >

[jira] [Commented] (SPARK-23863) Wholetext mode should not add line breaks

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

[jira] [Created] (SPARK-23863) Wholetext mode should not add line breaks

chencheng created SPARK-23863: - Summary: Wholetext mode should not add line breaks Key: SPARK-23863 URL: https://issues.apache.org/jira/browse/SPARK-23863 Project: Spark Issue Type: Bug

[jira] [Resolved] (SPARK-21351) Update nullability based on children's output in optimized logical plan

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

[jira] [Assigned] (SPARK-21351) Update nullability based on children's output in optimized logical plan

[ https://issues.apache.org/jira/browse/SPARK-21351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-21351: --- Assignee: Takeshi Yamamuro > Update nullability based on children's output in optimized

[jira] [Assigned] (SPARK-23826) TestHiveSparkSession should set default session

[ https://issues.apache.org/jira/browse/SPARK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-23826: --- Assignee: Xiao Li > TestHiveSparkSession should set default session >

[jira] [Resolved] (SPARK-23826) TestHiveSparkSession should set default session

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