[jira] [Assigned] (SPARK-39167) Throw an exception w/ an error class for multiple rows from a subquery used as an expression

[ https://issues.apache.org/jira/browse/SPARK-39167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Gekk reassigned SPARK-39167: Assignee: panbingkun > Throw an exception w/ an error class for multiple rows from a subquery

[jira] [Resolved] (SPARK-39167) Throw an exception w/ an error class for multiple rows from a subquery used as an expression

[ https://issues.apache.org/jira/browse/SPARK-39167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Gekk resolved SPARK-39167. -- Fix Version/s: 3.4.0 Resolution: Fixed Issue resolved by pull request 36580

[jira] [Commented] (SPARK-39245) Support Avro file scans with DEFAULT values

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

[jira] [Assigned] (SPARK-39245) Support Avro file scans with DEFAULT values

[ https://issues.apache.org/jira/browse/SPARK-39245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39245: Assignee: Apache Spark > Support Avro file scans with DEFAULT values >

[jira] [Assigned] (SPARK-39245) Support Avro file scans with DEFAULT values

[ https://issues.apache.org/jira/browse/SPARK-39245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39245: Assignee: (was: Apache Spark) > Support Avro file scans with DEFAULT values >

[jira] [Created] (SPARK-39245) Support Avro file scans with DEFAULT values

Daniel created SPARK-39245: -- Summary: Support Avro file scans with DEFAULT values Key: SPARK-39245 URL: https://issues.apache.org/jira/browse/SPARK-39245 Project: Spark Issue Type: Sub-task

[jira] [Assigned] (SPARK-39244) Use `--no-echo` instead of `--slave` in R 4.0

[ https://issues.apache.org/jira/browse/SPARK-39244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39244: Assignee: (was: Apache Spark) > Use `--no-echo` instead of `--slave` in R 4.0 >

[jira] [Assigned] (SPARK-39244) Use `--no-echo` instead of `--slave` in R 4.0

[ https://issues.apache.org/jira/browse/SPARK-39244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39244: Assignee: Apache Spark > Use `--no-echo` instead of `--slave` in R 4.0 >

[jira] [Commented] (SPARK-39244) Use `--no-echo` instead of `--slave` in R 4.0

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

[jira] [Commented] (SPARK-39244) Use `--no-echo` instead of `--slave` in R 4.0

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

[jira] [Created] (SPARK-39244) Use `--no-echo` instead of `--slave` in R 4.0

William Hyun created SPARK-39244: Summary: Use `--no-echo` instead of `--slave` in R 4.0 Key: SPARK-39244 URL: https://issues.apache.org/jira/browse/SPARK-39244 Project: Spark Issue Type:

[jira] [Assigned] (SPARK-39243) Describe the rules of quoting elements in error messages

[ https://issues.apache.org/jira/browse/SPARK-39243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39243: Assignee: (was: Apache Spark) > Describe the rules of quoting elements in error

[jira] [Assigned] (SPARK-39243) Describe the rules of quoting elements in error messages

[ https://issues.apache.org/jira/browse/SPARK-39243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39243: Assignee: Apache Spark > Describe the rules of quoting elements in error messages >

[jira] [Commented] (SPARK-39243) Describe the rules of quoting elements in error messages

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

[jira] [Created] (SPARK-39243) Describe the rules of quoting elements in error messages

Max Gekk created SPARK-39243: Summary: Describe the rules of quoting elements in error messages Key: SPARK-39243 URL: https://issues.apache.org/jira/browse/SPARK-39243 Project: Spark Issue Type:

[jira] [Assigned] (SPARK-39213) Create ANY_VALUE aggregate function

[ https://issues.apache.org/jira/browse/SPARK-39213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Gekk reassigned SPARK-39213: Assignee: Vitalii Li > Create ANY_VALUE aggregate function > ---

[jira] [Resolved] (SPARK-39213) Create ANY_VALUE aggregate function

[ https://issues.apache.org/jira/browse/SPARK-39213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Gekk resolved SPARK-39213. -- Fix Version/s: 3.4.0 Resolution: Fixed Issue resolved by pull request 36584

[jira] [Assigned] (SPARK-39242) AwaitOffset does not wait correctly for atleast expected offset and RateStreamProvider test is flaky

[ https://issues.apache.org/jira/browse/SPARK-39242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39242: Assignee: Apache Spark > AwaitOffset does not wait correctly for atleast expected offset

[jira] [Commented] (SPARK-39242) AwaitOffset does not wait correctly for atleast expected offset and RateStreamProvider test is flaky

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

[jira] [Commented] (SPARK-39242) AwaitOffset does not wait correctly for atleast expected offset and RateStreamProvider test is flaky

[ https://issues.apache.org/jira/browse/SPARK-39242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540252#comment-17540252 ] Anish Shrigondekar commented on SPARK-39242: PR for the change submitted here:

[jira] [Assigned] (SPARK-39242) AwaitOffset does not wait correctly for atleast expected offset and RateStreamProvider test is flaky

[ https://issues.apache.org/jira/browse/SPARK-39242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39242: Assignee: (was: Apache Spark) > AwaitOffset does not wait correctly for atleast

[jira] [Updated] (SPARK-39199) Implement pandas API missing parameters

[ https://issues.apache.org/jira/browse/SPARK-39199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinrong Meng updated SPARK-39199: - Description: pandas API on Spark aims to make pandas code work on Spark clusters without any

[jira] [Commented] (SPARK-39242) AwaitOffset does not wait correctly for atleast expected offset and RateStreamProvider test is flaky

[ https://issues.apache.org/jira/browse/SPARK-39242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540231#comment-17540231 ] Anish Shrigondekar commented on SPARK-39242: I have found the root cause for the issue and

[jira] [Created] (SPARK-39242) AwaitOffset does not wait correctly for atleast expected offset and RateStreamProvider test is flaky

Anish Shrigondekar created SPARK-39242: -- Summary: AwaitOffset does not wait correctly for atleast expected offset and RateStreamProvider test is flaky Key: SPARK-39242 URL:

[jira] [Resolved] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

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

[jira] [Assigned] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

[ https://issues.apache.org/jira/browse/SPARK-39240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen reassigned SPARK-39240: Assignee: Kent Yao > Source and binary releases using different tool to generates hashes

[jira] [Updated] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

[ https://issues.apache.org/jira/browse/SPARK-39240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-39240: - Issue Type: Improvement (was: Bug) Priority: Trivial (was: Major) > Source and binary

[jira] [Updated] (SPARK-39241) Spark SQL 'Like' operator behaves wrongly while filtering on partitioned column after Spark 3.1

[ https://issues.apache.org/jira/browse/SPARK-39241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Gorbatsevich updated SPARK-39241: Description: It seems like introduction of "like any" in spark 3.1 breaks "like"

[jira] [Created] (SPARK-39241) Spark SQL 'Like' operator behaves wrongly while filtering on partitioned column after Spark 3.1

Dmitry Gorbatsevich created SPARK-39241: --- Summary: Spark SQL 'Like' operator behaves wrongly while filtering on partitioned column after Spark 3.1 Key: SPARK-39241 URL:

[jira] [Commented] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

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

[jira] [Assigned] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

[ https://issues.apache.org/jira/browse/SPARK-39240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39240: Assignee: (was: Apache Spark) > Source and binary releases using different tool to

[jira] [Assigned] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

[ https://issues.apache.org/jira/browse/SPARK-39240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-39240: Assignee: Apache Spark > Source and binary releases using different tool to generates

[jira] [Commented] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

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

[jira] [Commented] (SPARK-38687) Use error classes in the compilation errors of generators

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

[jira] [Commented] (SPARK-39237) Update the ANSI SQL mode documentation

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

[jira] [Commented] (SPARK-39237) Update the ANSI SQL mode documentation

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

[jira] [Created] (SPARK-39240) Source and binary releases using different tool to generates hashes for integrity

Kent Yao created SPARK-39240: Summary: Source and binary releases using different tool to generates hashes for integrity Key: SPARK-39240 URL: https://issues.apache.org/jira/browse/SPARK-39240 Project:

[jira] [Assigned] (SPARK-38687) Use error classes in the compilation errors of generators

[ https://issues.apache.org/jira/browse/SPARK-38687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-38687: Assignee: (was: Apache Spark) > Use error classes in the compilation errors of

[jira] [Commented] (SPARK-38687) Use error classes in the compilation errors of generators

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

[jira] [Assigned] (SPARK-38687) Use error classes in the compilation errors of generators

[ https://issues.apache.org/jira/browse/SPARK-38687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-38687: Assignee: Apache Spark > Use error classes in the compilation errors of generators >

[jira] [Resolved] (SPARK-39237) Update the ANSI SQL mode documentation

[ https://issues.apache.org/jira/browse/SPARK-39237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gengliang Wang resolved SPARK-39237. Fix Version/s: 3.3.0 Resolution: Fixed Issue resolved by pull request 36614

[jira] [Updated] (SPARK-39239) Parquet written by spark in yarn mode can not be read by spark in local[2+] mode

[ https://issues.apache.org/jira/browse/SPARK-39239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kondziolka9ld updated SPARK-39239: -- Description: Hi, I came across a strange issue, namely data written by spark in yarn mode can

[jira] [Updated] (SPARK-39239) Parquet written by spark in yarn mode can not be read by spark in local[2+] mode

[ https://issues.apache.org/jira/browse/SPARK-39239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kondziolka9ld updated SPARK-39239: -- Description: Hi, I came across a strange issue, namely data written by spark in yarn mode can

[jira] [Updated] (SPARK-39239) Parquet written by spark in yarn mode can not be read by spark in local[2+] mode

[ https://issues.apache.org/jira/browse/SPARK-39239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kondziolka9ld updated SPARK-39239: -- Description: Hi, I came across a strange issue, namely data written by spark in yarn mode can

[jira] [Updated] (SPARK-39239) Parquet written by spark in yarn mode can not be read by spark in local[2+] mode

[ https://issues.apache.org/jira/browse/SPARK-39239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kondziolka9ld updated SPARK-39239: -- Attachment: threaddump_spark_shell > Parquet written by spark in yarn mode can not be read by

[jira] [Created] (SPARK-39239) Parquet written by spark in yarn mode can not be read by spark in local[2+] mode

kondziolka9ld created SPARK-39239: - Summary: Parquet written by spark in yarn mode can not be read by spark in local[2+] mode Key: SPARK-39239 URL: https://issues.apache.org/jira/browse/SPARK-39239