[jira] [Assigned] (SPARK-20640) Make rpc timeout and retry for shuffle registration configurable

[ https://issues.apache.org/jira/browse/SPARK-20640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20640: Assignee: Apache Spark > Make rpc timeout and retry for shuffle registration configurable

[jira] [Assigned] (SPARK-20640) Make rpc timeout and retry for shuffle registration configurable

[ https://issues.apache.org/jira/browse/SPARK-20640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20640: Assignee: (was: Apache Spark) > Make rpc timeout and retry for shuffle registration

[jira] [Closed] (SPARK-20565) Improve the error message for unsupported JDBC types

[ https://issues.apache.org/jira/browse/SPARK-20565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li closed SPARK-20565. --- Resolution: Fixed Fix Version/s: 2.3.0 > Improve the error message for unsupported JDBC types >

[jira] [Commented] (SPARK-20640) Make rpc timeout and retry for shuffle registration configurable

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

[jira] [Commented] (SPARK-20565) Improve the error message for unsupported JDBC types

[ https://issues.apache.org/jira/browse/SPARK-20565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024215#comment-16024215 ] Xiao Li commented on SPARK-20565: - Fixed in https://github.com/apache/spark/pull/17835 > Improve the

[jira] [Created] (SPARK-20878) Pyspark date string parsing erroneously treats 1 as 10

Nick Lothian created SPARK-20878: Summary: Pyspark date string parsing erroneously treats 1 as 10 Key: SPARK-20878 URL: https://issues.apache.org/jira/browse/SPARK-20878 Project: Spark

[jira] [Updated] (SPARK-20876) if the input parameter is float type for ceil or floor ,the result is not we expected

[ https://issues.apache.org/jira/browse/SPARK-20876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuxian updated SPARK-20876: Description: spark-sql>SELECT ceil(cast(12345.1233 as float)); spark-sql>12345 For this case, the result

[jira] [Updated] (SPARK-20876) if the input parameter is float type for ceil ,the result is not we expected

[ https://issues.apache.org/jira/browse/SPARK-20876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuxian updated SPARK-20876: Description: spark-sql>SELECT ceil(cast(12345.1233 as float)); spark-sql>12345 For this case, we expected

[jira] [Commented] (SPARK-4131) Support "Writing data into the filesystem from queries"

[ https://issues.apache.org/jira/browse/SPARK-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024212#comment-16024212 ] Santhavathi S commented on SPARK-4131: -- Is this feature available yet? > Support "Writing data into

[jira] [Updated] (SPARK-20876) if the input parameter is float type for ceil or floor ,the result is not we expected

[ https://issues.apache.org/jira/browse/SPARK-20876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuxian updated SPARK-20876: Summary: if the input parameter is float type for ceil or floor ,the result is not we expected (was: if

[jira] [Assigned] (SPARK-20873) Improve the error message for unsupported Column Type

[ https://issues.apache.org/jira/browse/SPARK-20873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li reassigned SPARK-20873: --- Assignee: (was: Xiao Li) > Improve the error message for unsupported Column Type >

[jira] [Assigned] (SPARK-20877) Investigate if tests will time out on CRAN

[ https://issues.apache.org/jira/browse/SPARK-20877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20877: Assignee: Apache Spark > Investigate if tests will time out on CRAN >

[jira] [Assigned] (SPARK-20877) Investigate if tests will time out on CRAN

[ https://issues.apache.org/jira/browse/SPARK-20877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20877: Assignee: (was: Apache Spark) > Investigate if tests will time out on CRAN >

[jira] [Commented] (SPARK-20877) Investigate if tests will time out on CRAN

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

[jira] [Created] (SPARK-20877) Investigate if tests will time out on CRAN

Felix Cheung created SPARK-20877: Summary: Investigate if tests will time out on CRAN Key: SPARK-20877 URL: https://issues.apache.org/jira/browse/SPARK-20877 Project: Spark Issue Type:

[jira] [Assigned] (SPARK-20876) if the input parameter is float type for ceil ,the result is not we expected

[ https://issues.apache.org/jira/browse/SPARK-20876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20876: Assignee: (was: Apache Spark) > if the input parameter is float type for ceil ,the

[jira] [Assigned] (SPARK-20876) if the input parameter is float type for ceil ,the result is not we expected

[ https://issues.apache.org/jira/browse/SPARK-20876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20876: Assignee: Apache Spark > if the input parameter is float type for ceil ,the result is

[jira] [Commented] (SPARK-20876) if the input parameter is float type for ceil ,the result is not we expected

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

[jira] [Created] (SPARK-20876) if the input parameter is float type for ceil ,the result is not we expected

liuxian created SPARK-20876: --- Summary: if the input parameter is float type for ceil ,the result is not we expected Key: SPARK-20876 URL: https://issues.apache.org/jira/browse/SPARK-20876 Project: Spark

[jira] [Assigned] (SPARK-20875) Spark should print the log when the directory has been deleted

[ https://issues.apache.org/jira/browse/SPARK-20875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20875: Assignee: Apache Spark > Spark should print the log when the directory has been deleted >

[jira] [Assigned] (SPARK-20875) Spark should print the log when the directory has been deleted

[ https://issues.apache.org/jira/browse/SPARK-20875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20875: Assignee: (was: Apache Spark) > Spark should print the log when the directory has

[jira] [Commented] (SPARK-20875) Spark should print the log when the directory has been deleted

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

[jira] [Created] (SPARK-20875) Spark should print the log when the directory has been deleted

liuzhaokun created SPARK-20875: -- Summary: Spark should print the log when the directory has been deleted Key: SPARK-20875 URL: https://issues.apache.org/jira/browse/SPARK-20875 Project: Spark

[jira] [Commented] (SPARK-18105) LZ4 failed to decompress a stream of shuffled data

[ https://issues.apache.org/jira/browse/SPARK-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023980#comment-16023980 ] Rupesh Mane commented on SPARK-18105: - For the stack provided earlier, I found the root cause: Issue

[jira] [Assigned] (SPARK-20874) The "examples" project doesn't depend on Structured Streaming Kafka source

[ https://issues.apache.org/jira/browse/SPARK-20874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20874: Assignee: Shixiong Zhu (was: Apache Spark) > The "examples" project doesn't depend on

[jira] [Assigned] (SPARK-20874) The "examples" project doesn't depend on Structured Streaming Kafka source

[ https://issues.apache.org/jira/browse/SPARK-20874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20874: Assignee: Apache Spark (was: Shixiong Zhu) > The "examples" project doesn't depend on

[jira] [Commented] (SPARK-20874) The "examples" project doesn't depend on Structured Streaming Kafka source

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

[jira] [Created] (SPARK-20874) The "examples" project doesn't depend on Structured Streaming Kafka source

Shixiong Zhu created SPARK-20874: Summary: The "examples" project doesn't depend on Structured Streaming Kafka source Key: SPARK-20874 URL: https://issues.apache.org/jira/browse/SPARK-20874 Project:

[jira] [Resolved] (SPARK-20403) It is wrong to the instructions of some functions,such as boolean，tinyint，smallint，int，bigint，float，double，decimal，date，timestamp，binary，string

[ https://issues.apache.org/jira/browse/SPARK-20403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li resolved SPARK-20403. - Resolution: Fixed Assignee: liuxian Fix Version/s: 2.2.0 > It is wrong to the

[jira] [Updated] (SPARK-18406) Race between end-of-task and completion iterator read lock release

[ https://issues.apache.org/jira/browse/SPARK-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan updated SPARK-18406: Fix Version/s: 2.1.2 > Race between end-of-task and completion iterator read lock release >

[jira] [Resolved] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

[ https://issues.apache.org/jira/browse/SPARK-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li resolved SPARK-20872. - Resolution: Fixed Fix Version/s: 2.2.0 > ShuffleExchange.nodeName should handle null coordinator

[jira] [Assigned] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

[ https://issues.apache.org/jira/browse/SPARK-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li reassigned SPARK-20872: --- Assignee: Kris Mok > ShuffleExchange.nodeName should handle null coordinator >

[jira] [Resolved] (SPARK-20205) DAGScheduler posts SparkListenerStageSubmitted before updating stage

[ https://issues.apache.org/jira/browse/SPARK-20205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin resolved SPARK-20205. Resolution: Fixed Assignee: Marcelo Vanzin Fix Version/s: 2.3.0 >

[jira] [Commented] (SPARK-20848) Dangling threads when reading parquet files in local mode

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

[jira] [Commented] (SPARK-20589) Allow limiting task concurrency per stage

[ https://issues.apache.org/jira/browse/SPARK-20589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023769#comment-16023769 ] Mark Nelson commented on SPARK-20589: - I would find this very useful. We're currently using coalesce

[jira] [Commented] (SPARK-18406) Race between end-of-task and completion iterator read lock release

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

[jira] [Updated] (SPARK-18406) Race between end-of-task and completion iterator read lock release

[ https://issues.apache.org/jira/browse/SPARK-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-18406: Fix Version/s: 2.0.3 > Race between end-of-task and completion iterator read lock release >

[jira] [Assigned] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16944: Assignee: (was: Apache Spark) > [MESOS] Improve data locality when launching new

[jira] [Assigned] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16944: Assignee: Apache Spark > [MESOS] Improve data locality when launching new executors when

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

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

[jira] [Updated] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

[ https://issues.apache.org/jira/browse/SPARK-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kris Mok updated SPARK-20872: - Description: A ShuffleExchange's coordinator can be null sometimes, and when we need to do a toString()

[jira] [Commented] (SPARK-20873) Improve the error message for unsupported Column Type

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

[jira] [Assigned] (SPARK-20873) Improve the error message for unsupported Column Type

[ https://issues.apache.org/jira/browse/SPARK-20873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20873: Assignee: Apache Spark (was: Xiao Li) > Improve the error message for unsupported Column

[jira] [Assigned] (SPARK-20873) Improve the error message for unsupported Column Type

[ https://issues.apache.org/jira/browse/SPARK-20873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20873: Assignee: Xiao Li (was: Apache Spark) > Improve the error message for unsupported Column

[jira] [Updated] (SPARK-20873) Improve the error message for unsupported Column Type

[ https://issues.apache.org/jira/browse/SPARK-20873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruben Janssen updated SPARK-20873: -- Description: For unsupported column type, we simply output the column type instead of the

[jira] [Updated] (SPARK-20873) Improve the error message for unsupported Column Type

[ https://issues.apache.org/jira/browse/SPARK-20873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruben Janssen updated SPARK-20873: -- Description: For unsupported column type, we simply output the column type instead of the

[jira] [Updated] (SPARK-20873) Improve the error message for unsupported Column Type

[ https://issues.apache.org/jira/browse/SPARK-20873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruben Janssen updated SPARK-20873: -- Description: For unsupported column type, we simply output the column type instead of the

[jira] [Created] (SPARK-20873) Improve the error message for unsupported Column Type

Ruben Janssen created SPARK-20873: - Summary: Improve the error message for unsupported Column Type Key: SPARK-20873 URL: https://issues.apache.org/jira/browse/SPARK-20873 Project: Spark

[jira] [Commented] (SPARK-18406) Race between end-of-task and completion iterator read lock release

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

[jira] [Closed] (SPARK-6000) Batch K-Means clusters should support "mini-batch" updates

[ https://issues.apache.org/jira/browse/SPARK-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Pentreath closed SPARK-6000. - Resolution: Duplicate > Batch K-Means clusters should support "mini-batch" updates >

[jira] [Commented] (SPARK-14174) Accelerate KMeans via Mini-Batch EM

[ https://issues.apache.org/jira/browse/SPARK-14174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023454#comment-16023454 ] Nick Pentreath commented on SPARK-14174: It makes sense. However, I think k=100 is perhaps less

[jira] [Assigned] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

[ https://issues.apache.org/jira/browse/SPARK-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20872: Assignee: Apache Spark > ShuffleExchange.nodeName should handle null coordinator >

[jira] [Assigned] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

[ https://issues.apache.org/jira/browse/SPARK-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20872: Assignee: (was: Apache Spark) > ShuffleExchange.nodeName should handle null

[jira] [Commented] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

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

[jira] [Commented] (SPARK-20866) Dataset map does not respect nullable field

[ https://issues.apache.org/jira/browse/SPARK-20866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023435#comment-16023435 ] Kazuaki Ishizaki commented on SPARK-20866: -- I confirmed that it has been fixed in master branch.

[jira] [Commented] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

[ https://issues.apache.org/jira/browse/SPARK-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023421#comment-16023421 ] Kris Mok commented on SPARK-20872: -- The said matching logic in ShuffleExchange.nodeName() is introduced

[jira] [Created] (SPARK-20872) ShuffleExchange.nodeName should handle null coordinator

Kris Mok created SPARK-20872: Summary: ShuffleExchange.nodeName should handle null coordinator Key: SPARK-20872 URL: https://issues.apache.org/jira/browse/SPARK-20872 Project: Spark Issue Type:

[jira] [Assigned] (SPARK-20775) from_json should also have an API where the schema is specified with a string

[ https://issues.apache.org/jira/browse/SPARK-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20775: Assignee: Apache Spark > from_json should also have an API where the schema is specified

[jira] [Updated] (SPARK-20865) caching dataset throws "Queries with streaming sources must be executed with writeStream.start()"

[ https://issues.apache.org/jira/browse/SPARK-20865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Armbrust updated SPARK-20865: - Description: {code} SparkSession .builder .master("local[*]")

[jira] [Assigned] (SPARK-20775) from_json should also have an API where the schema is specified with a string

[ https://issues.apache.org/jira/browse/SPARK-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20775: Assignee: (was: Apache Spark) > from_json should also have an API where the schema is

[jira] [Commented] (SPARK-20775) from_json should also have an API where the schema is specified with a string

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

[jira] [Commented] (SPARK-4899) Support Mesos features: roles and checkpoints

[ https://issues.apache.org/jira/browse/SPARK-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023383#comment-16023383 ] Michael Gummelt commented on SPARK-4899: Thanks Kamal. I responded to the thread, which I'll copy

[jira] [Commented] (SPARK-20815) NullPointerException in RPackageUtils#checkManifestForR

[ https://issues.apache.org/jira/browse/SPARK-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023343#comment-16023343 ] Felix Cheung commented on SPARK-20815: -- Thanks Sean > NullPointerException in

[jira] [Assigned] (SPARK-20815) NullPointerException in RPackageUtils#checkManifestForR

[ https://issues.apache.org/jira/browse/SPARK-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Cheung reassigned SPARK-20815: Assignee: James Shuster > NullPointerException in RPackageUtils#checkManifestForR >

[jira] [Assigned] (SPARK-20774) BroadcastExchangeExec doesn't cancel the Spark job if broadcasting a relation timeouts.

[ https://issues.apache.org/jira/browse/SPARK-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20774: Assignee: (was: Apache Spark) > BroadcastExchangeExec doesn't cancel the Spark job if

[jira] [Assigned] (SPARK-20774) BroadcastExchangeExec doesn't cancel the Spark job if broadcasting a relation timeouts.

[ https://issues.apache.org/jira/browse/SPARK-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20774: Assignee: Apache Spark > BroadcastExchangeExec doesn't cancel the Spark job if

[jira] [Commented] (SPARK-20774) BroadcastExchangeExec doesn't cancel the Spark job if broadcasting a relation timeouts.

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

[jira] [Commented] (SPARK-20660) Not able to merge Dataframes with different column orders

[ https://issues.apache.org/jira/browse/SPARK-20660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1602#comment-1602 ] Michel Lemay commented on SPARK-20660: -- In my opinion, two schema should be considered the same if

[jira] [Comment Edited] (SPARK-20871) Only log Janino code in debug mode

[ https://issues.apache.org/jira/browse/SPARK-20871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023306#comment-16023306 ] Glen Takahashi edited comment on SPARK-20871 at 5/24/17 5:46 PM: - Just

[jira] [Updated] (SPARK-20871) Only log Janino code in debug mode

[ https://issues.apache.org/jira/browse/SPARK-20871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glen Takahashi updated SPARK-20871: --- Attachment: 6a57e344-3fcf-11e7-85cc-52a06df2a489.png An example of Janino logging adding

[jira] [Created] (SPARK-20871) Only log Janino code in debug mode

Glen Takahashi created SPARK-20871: -- Summary: Only log Janino code in debug mode Key: SPARK-20871 URL: https://issues.apache.org/jira/browse/SPARK-20871 Project: Spark Issue Type:

[jira] [Updated] (SPARK-20870) Update the output of spark-sql -H

[ https://issues.apache.org/jira/browse/SPARK-20870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-20870: Labels: starter (was: ) > Update the output of spark-sql -H > - > >

[jira] [Created] (SPARK-20870) Update the output of spark-sql -H

Xiao Li created SPARK-20870: --- Summary: Update the output of spark-sql -H Key: SPARK-20870 URL: https://issues.apache.org/jira/browse/SPARK-20870 Project: Spark Issue Type: Bug

[jira] [Comment Edited] (SPARK-20660) Not able to merge Dataframes with different column orders

[ https://issues.apache.org/jira/browse/SPARK-20660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023230#comment-16023230 ] lyc edited comment on SPARK-20660 at 5/24/17 5:02 PM: -- Do you expect spark to fail

[jira] [Commented] (SPARK-20660) Not able to merge Dataframes with different column orders

[ https://issues.apache.org/jira/browse/SPARK-20660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023230#comment-16023230 ] lyc commented on SPARK-20660: - Do you expect spark to fail the query? > Not able to merge Dataframes with

[jira] [Updated] (SPARK-20869) Master may clear failed apps when worker down

[ https://issues.apache.org/jira/browse/SPARK-20869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lyc updated SPARK-20869: Summary: Master may clear failed apps when worker down (was: Master should clear failed apps when worker down) >

[jira] [Updated] (SPARK-20869) Master should clear failed apps when worker down

[ https://issues.apache.org/jira/browse/SPARK-20869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lyc updated SPARK-20869: Remaining Estimate: 2h (was: 24h) Original Estimate: 2h (was: 24h) > Master should clear failed apps when

[jira] [Updated] (SPARK-20869) Master should clear failed apps when worker down

[ https://issues.apache.org/jira/browse/SPARK-20869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lyc updated SPARK-20869: Description: In `Master.removeWorker`, master clears executor and driver state, but does not clear app state. App

[jira] [Updated] (SPARK-20869) Master should clear failed apps when worker down

[ https://issues.apache.org/jira/browse/SPARK-20869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lyc updated SPARK-20869: Description: In `Master.removeWorker`, master clears executor and driver state, but does not clear app state. App

[jira] [Created] (SPARK-20869) Master should clear failed apps when worker down

lyc created SPARK-20869: --- Summary: Master should clear failed apps when worker down Key: SPARK-20869 URL: https://issues.apache.org/jira/browse/SPARK-20869 Project: Spark Issue Type: Improvement

[jira] [Resolved] (SPARK-20848) Dangling threads when reading parquet files in local mode

[ https://issues.apache.org/jira/browse/SPARK-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan resolved SPARK-20848. - Resolution: Fixed Assignee: Liang-Chi Hsieh Fix Version/s: 2.2.0

[jira] [Assigned] (SPARK-20868) UnsafeShuffleWriter should verify the position after FileChannel.transferTo

[ https://issues.apache.org/jira/browse/SPARK-20868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20868: Assignee: Apache Spark (was: Wenchen Fan) > UnsafeShuffleWriter should verify the

[jira] [Commented] (SPARK-20868) UnsafeShuffleWriter should verify the position after FileChannel.transferTo

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

[jira] [Assigned] (SPARK-20868) UnsafeShuffleWriter should verify the position after FileChannel.transferTo

[ https://issues.apache.org/jira/browse/SPARK-20868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20868: Assignee: Wenchen Fan (was: Apache Spark) > UnsafeShuffleWriter should verify the

[jira] [Created] (SPARK-20868) UnsafeShuffleWriter should verify the position after FileChannel.transferTo

Wenchen Fan created SPARK-20868: --- Summary: UnsafeShuffleWriter should verify the position after FileChannel.transferTo Key: SPARK-20868 URL: https://issues.apache.org/jira/browse/SPARK-20868 Project:

[jira] [Updated] (SPARK-20866) Dataset map does not respect nullable field

[ https://issues.apache.org/jira/browse/SPARK-20866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Breame updated SPARK-20866: - Description: The Dataset.map does not respect the nullable fields within the schema. *Test

[jira] [Assigned] (SPARK-20250) Improper OOM error when a task been killed while spilling data

[ https://issues.apache.org/jira/browse/SPARK-20250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20250: Assignee: (was: Apache Spark) > Improper OOM error when a task been killed while

[jira] [Assigned] (SPARK-20250) Improper OOM error when a task been killed while spilling data

[ https://issues.apache.org/jira/browse/SPARK-20250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20250: Assignee: Apache Spark > Improper OOM error when a task been killed while spilling data >

[jira] [Commented] (SPARK-20250) Improper OOM error when a task been killed while spilling data

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

[jira] [Comment Edited] (SPARK-18105) LZ4 failed to decompress a stream of shuffled data

[ https://issues.apache.org/jira/browse/SPARK-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023072#comment-16023072 ] Wenchen Fan edited comment on SPARK-18105 at 5/24/17 3:13 PM: -- can you try

[jira] [Comment Edited] (SPARK-18105) LZ4 failed to decompress a stream of shuffled data

[ https://issues.apache.org/jira/browse/SPARK-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023072#comment-16023072 ] Wenchen Fan edited comment on SPARK-18105 at 5/24/17 3:13 PM: -- can you try

[jira] [Commented] (SPARK-18105) LZ4 failed to decompress a stream of shuffled data

[ https://issues.apache.org/jira/browse/SPARK-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023072#comment-16023072 ] Wenchen Fan commented on SPARK-18105: - can you try to set {{{spark.file.transferTo}}} to false and

[jira] [Comment Edited] (SPARK-18105) LZ4 failed to decompress a stream of shuffled data

[ https://issues.apache.org/jira/browse/SPARK-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023072#comment-16023072 ] Wenchen Fan edited comment on SPARK-18105 at 5/24/17 3:12 PM: -- can you try

[jira] [Commented] (SPARK-19281) spark.ml Python API for FPGrowth

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

[jira] [Resolved] (SPARK-20862) LogisticRegressionModel throws TypeError

[ https://issues.apache.org/jira/browse/SPARK-20862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang resolved SPARK-20862. - Resolution: Fixed Fix Version/s: 2.2.0 2.1.2 2.0.3

[jira] [Assigned] (SPARK-20862) LogisticRegressionModel throws TypeError

[ https://issues.apache.org/jira/browse/SPARK-20862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang reassigned SPARK-20862: --- Assignee: Bago Amirbekian > LogisticRegressionModel throws TypeError >

[jira] [Assigned] (SPARK-20768) PySpark FPGrowth does not expose numPartitions (expert) param

[ https://issues.apache.org/jira/browse/SPARK-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang reassigned SPARK-20768: --- Assignee: Yan Facai (颜发才) > PySpark FPGrowth does not expose numPartitions (expert) param

[jira] [Updated] (SPARK-20799) Unable to infer schema for ORC on S3N when secrets are in the URL

[ https://issues.apache.org/jira/browse/SPARK-20799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated SPARK-20799: --- Summary: Unable to infer schema for ORC on S3N when secrets are in the URL (was: Unable to

[jira] [Assigned] (SPARK-20867) Move individual hints from Statistics into HintInfo class

[ https://issues.apache.org/jira/browse/SPARK-20867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20867: Assignee: Apache Spark (was: Reynold Xin) > Move individual hints from Statistics into

[jira] [Assigned] (SPARK-20867) Move individual hints from Statistics into HintInfo class

[ https://issues.apache.org/jira/browse/SPARK-20867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-20867: Assignee: Reynold Xin (was: Apache Spark) > Move individual hints from Statistics into

  1   2   >