[jira] [Commented] (SPARK-44817) Incremental Stats Collection

[ https://issues.apache.org/jira/browse/SPARK-44817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766213#comment-17766213 ] Rakesh Raushan commented on SPARK-44817: [~gurwls223] [~cloud_fan] [~dongjoon] I have added an

[jira] [Updated] (SPARK-43979) CollectedMetrics should be treated as the same one for self-join

[ https://issues.apache.org/jira/browse/SPARK-43979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-43979: --- Labels: pull-request-available (was: ) > CollectedMetrics should be treated as the same

[jira] [Updated] (SPARK-45194) Parquet reads fail with "RuntimeException: Unable to create Parquet converter for data type "timestamp_ntz" due to incorrect schema inference

[ https://issues.apache.org/jira/browse/SPARK-45194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Sadikov updated SPARK-45194: - Description: I found that Parquet reads could fail due to incorrect schema inference with two

[jira] [Updated] (SPARK-45194) Parquet reads fail with "RuntimeException: Unable to create Parquet converter for data type "timestamp_ntz" due to incorrect schema inference

[ https://issues.apache.org/jira/browse/SPARK-45194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Sadikov updated SPARK-45194: - Description: I found that Parquet reads could fail due to incorrect schema inference with two

[jira] [Commented] (SPARK-45194) Parquet reads fail with "RuntimeException: Unable to create Parquet converter for data type "timestamp_ntz" due to incorrect schema inference

[ https://issues.apache.org/jira/browse/SPARK-45194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766198#comment-17766198 ] Ivan Sadikov commented on SPARK-45194: -- cc [~gengliang] [~cloud_fan] > Parquet reads fail with

[jira] [Created] (SPARK-45194) Parquet reads fail with "RuntimeException: Unable to create Parquet converter for data type "timestamp_ntz" due to incorrect schema inference

Ivan Sadikov created SPARK-45194: Summary: Parquet reads fail with "RuntimeException: Unable to create Parquet converter for data type "timestamp_ntz" due to incorrect schema inference Key: SPARK-45194 URL:

[jira] [Updated] (SPARK-45193) Refactor `test_mode` to be compatible with Spark Connect

[ https://issues.apache.org/jira/browse/SPARK-45193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-45193: --- Labels: pull-request-available (was: ) > Refactor `test_mode` to be compatible with Spark

[jira] [Created] (SPARK-45193) Refactor `test_mode` to be compatible with Spark Connect

Ruifeng Zheng created SPARK-45193: - Summary: Refactor `test_mode` to be compatible with Spark Connect Key: SPARK-45193 URL: https://issues.apache.org/jira/browse/SPARK-45193 Project: Spark

[jira] [Resolved] (SPARK-45189) Creating UnresolvedRelation from TableIdentifier should include the catalog field

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

[jira] [Commented] (SPARK-45188) Update error messages related to parameterized sql()

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

[jira] [Updated] (SPARK-45188) Update error messages related to parameterized sql()

[ https://issues.apache.org/jira/browse/SPARK-45188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-45188: --- Labels: pull-request-available (was: ) > Update error messages related to parameterized

[jira] [Updated] (SPARK-45192) lineInterpolate for graphviz edge is overdue

[ https://issues.apache.org/jira/browse/SPARK-45192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-45192: --- Labels: pull-request-available (was: ) > lineInterpolate for graphviz edge is overdue >

[jira] [Updated] (SPARK-45192) lineInterpolate for graphviz edge is overdue

[ https://issues.apache.org/jira/browse/SPARK-45192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kent Yao updated SPARK-45192: - Priority: Trivial (was: Major) > lineInterpolate for graphviz edge is overdue >

[jira] [Created] (SPARK-45192) lineInterpolate for graphviz edge is overdue

Kent Yao created SPARK-45192: Summary: lineInterpolate for graphviz edge is overdue Key: SPARK-45192 URL: https://issues.apache.org/jira/browse/SPARK-45192 Project: Spark Issue Type: Bug

[jira] [Updated] (SPARK-45160) The default value of ‘spark.executor.logs.rolling.strategy’ on the official website is incorrect

[ https://issues.apache.org/jira/browse/SPARK-45160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-45160: - Issue Type: Improvement (was: Bug) Priority: Trivial (was: Minor) > The default value

[jira] [Resolved] (SPARK-45160) The default value of ‘spark.executor.logs.rolling.strategy’ on the official website is incorrect

[ https://issues.apache.org/jira/browse/SPARK-45160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen resolved SPARK-45160. -- Fix Version/s: 4.0.0 Assignee: chenyu Resolution: Fixed Resolved by

[jira] [Updated] (SPARK-45191) InMemoryTableScanExec simpleStringWithNodeId adds columnar info

[ https://issues.apache.org/jira/browse/SPARK-45191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-45191: --- Labels: pull-request-available (was: ) > InMemoryTableScanExec simpleStringWithNodeId adds

[jira] [Created] (SPARK-45191) InMemoryTableScanExec simpleStringWithNodeId adds columnar info

XiDuo You created SPARK-45191: - Summary: InMemoryTableScanExec simpleStringWithNodeId adds columnar info Key: SPARK-45191 URL: https://issues.apache.org/jira/browse/SPARK-45191 Project: Spark

[jira] [Resolved] (SPARK-45184) Remove orphaned error class documents

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

[jira] [Assigned] (SPARK-45184) Remove orphaned error class documents

[ https://issues.apache.org/jira/browse/SPARK-45184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-45184: --- Assignee: BingKun Pan > Remove orphaned error class documents >

[jira] [Updated] (SPARK-45134) Data duplication may occur when fallback to origin shuffle block

[ https://issues.apache.org/jira/browse/SPARK-45134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gaoyajun02 updated SPARK-45134: --- Priority: Critical (was: Blocker) > Data duplication may occur when fallback to origin shuffle

[jira] [Updated] (SPARK-45134) Data duplication may occur when fallback to origin shuffle block

[ https://issues.apache.org/jira/browse/SPARK-45134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gaoyajun02 updated SPARK-45134: --- Priority: Blocker (was: Critical) > Data duplication may occur when fallback to origin shuffle

[jira] [Created] (SPARK-45190) XML: StructType schema issue in pyspark connect

Sandip Agarwala created SPARK-45190: --- Summary: XML: StructType schema issue in pyspark connect Key: SPARK-45190 URL: https://issues.apache.org/jira/browse/SPARK-45190 Project: Spark Issue

[jira] [Updated] (SPARK-45134) Data duplication may occur when fallback to origin shuffle block

[ https://issues.apache.org/jira/browse/SPARK-45134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gaoyajun02 updated SPARK-45134: --- Priority: Critical (was: Major) > Data duplication may occur when fallback to origin shuffle block

[jira] [Updated] (SPARK-45134) Data duplication may occur when fallback to origin shuffle block

[ https://issues.apache.org/jira/browse/SPARK-45134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gaoyajun02 updated SPARK-45134: --- Affects Version/s: 3.5.0 3.4.0 3.3.0 > Data

[jira] [Updated] (SPARK-45160) The default value of ‘spark.executor.logs.rolling.strategy’ on the official website is incorrect

[ https://issues.apache.org/jira/browse/SPARK-45160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-45160: --- Labels: pull-request-available (was: ) > The default value of

[jira] [Commented] (SPARK-44752) XML: Update Spark Docs

[ https://issues.apache.org/jira/browse/SPARK-44752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766171#comment-17766171 ] Hyukjin Kwon commented on SPARK-44752: -- [~laglangyue] you can directly create a PR with this JIRA.

[jira] [Commented] (SPARK-44033) Support list-like for binary ops

[ https://issues.apache.org/jira/browse/SPARK-44033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766170#comment-17766170 ] Haejoon Lee commented on SPARK-44033: - No worries! Let me take a look soon. Thanks for working on

[jira] [Updated] (SPARK-44001) Improve parsing of well known wrapper types

[ https://issues.apache.org/jira/browse/SPARK-44001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-44001: --- Labels: pull-request-available (was: ) > Improve parsing of well known wrapper types >

[jira] [Updated] (SPARK-45189) Creating UnresolvedRelation from TableIdentifier should include the catalog field

[ https://issues.apache.org/jira/browse/SPARK-45189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-45189: --- Labels: pull-request-available (was: ) > Creating UnresolvedRelation from TableIdentifier

[jira] [Created] (SPARK-45189) Creating UnresolvedRelation from TableIdentifier should include the catalog field

Gengliang Wang created SPARK-45189: -- Summary: Creating UnresolvedRelation from TableIdentifier should include the catalog field Key: SPARK-45189 URL: https://issues.apache.org/jira/browse/SPARK-45189

[jira] [Commented] (SPARK-44033) Support list-like for binary ops

[ https://issues.apache.org/jira/browse/SPARK-44033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766159#comment-17766159 ] Gurpreet Singh commented on SPARK-44033: Hi [~itholic], Apologies for the delay on this. But I

[jira] [Updated] (SPARK-44033) Support list-like for binary ops

[ https://issues.apache.org/jira/browse/SPARK-44033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-44033: --- Labels: pull-request-available (was: ) > Support list-like for binary ops >

[jira] [Updated] (SPARK-44837) Improve error message for ALTER TABLE ALTER COLUMN on partition columns in non-delta tables

[ https://issues.apache.org/jira/browse/SPARK-44837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-44837: --- Labels: pull-request-available (was: ) > Improve error message for ALTER TABLE ALTER

[jira] [Resolved] (SPARK-45034) Support deterministic mode function

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

[jira] [Assigned] (SPARK-45034) Support deterministic mode function

[ https://issues.apache.org/jira/browse/SPARK-45034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Gekk reassigned SPARK-45034: Assignee: Peter Toth > Support deterministic mode function > ---

[jira] [Created] (SPARK-45188) Update error messages related to parameterized sql()

Max Gekk created SPARK-45188: Summary: Update error messages related to parameterized sql() Key: SPARK-45188 URL: https://issues.apache.org/jira/browse/SPARK-45188 Project: Spark Issue Type:

[jira] [Updated] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` urls

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-45187: -- Fix Version/s: 3.4.2 3.5.1 3.3.4 > Fix WorkerPage to

[jira] [Resolved] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` urls

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-45187. --- Fix Version/s: 4.0.0 Resolution: Fixed Issue resolved by pull request 42959

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` urls

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun reassigned SPARK-45187: - Assignee: Dongjoon Hyun > Fix WorkerPage to use the same pattern for `logPage` urls >

[jira] [Updated] (SPARK-44823) Update black to 23.7.0 and fix erroneous check

[ https://issues.apache.org/jira/browse/SPARK-44823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-44823: --- Labels: pull-request-available (was: ) > Update black to 23.7.0 and fix erroneous check >

[jira] [Updated] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` urls

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-45187: -- Summary: Fix WorkerPage to use the same pattern for `logPage` urls (was: Fix WorkerPage to

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: (was: Apache Spark) > Fix WorkerPage to use the same pattern for

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: Apache Spark > Fix WorkerPage to use the same pattern for `logPage` query

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: (was: Apache Spark) > Fix WorkerPage to use the same pattern for

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: (was: Apache Spark) > Fix WorkerPage to use the same pattern for

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: Apache Spark > Fix WorkerPage to use the same pattern for `logPage` query

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: Apache Spark > Fix WorkerPage to use the same pattern for `logPage` query

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: (was: Apache Spark) > Fix WorkerPage to use the same pattern for

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: Apache Spark > Fix WorkerPage to use the same pattern for `logPage` query

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: (was: Apache Spark) > Fix WorkerPage to use the same pattern for

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: Apache Spark > Fix WorkerPage to use the same pattern for `logPage` query

[jira] [Resolved] (SPARK-45167) Python Spark Connect client does not call `releaseAll`

[ https://issues.apache.org/jira/browse/SPARK-45167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-45167. --- Fix Version/s: 4.0.0 Resolution: Fixed Issue resolved by pull request 42929

[jira] [Assigned] (SPARK-45167) Python Spark Connect client does not call `releaseAll`

[ https://issues.apache.org/jira/browse/SPARK-45167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun reassigned SPARK-45167: - Assignee: Martin Grund > Python Spark Connect client does not call `releaseAll` >

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: Apache Spark > Fix WorkerPage to use the same pattern for `logPage` query

[jira] [Assigned] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot reassigned SPARK-45187: -- Assignee: (was: Apache Spark) > Fix WorkerPage to use the same pattern for

[jira] [Updated] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

[ https://issues.apache.org/jira/browse/SPARK-45187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-45187: --- Labels: pull-request-available (was: ) > Fix WorkerPage to use the same pattern for

[jira] [Created] (SPARK-45187) Fix WorkerPage to use the same pattern for `logPage` query parameters

Dongjoon Hyun created SPARK-45187: - Summary: Fix WorkerPage to use the same pattern for `logPage` query parameters Key: SPARK-45187 URL: https://issues.apache.org/jira/browse/SPARK-45187 Project:

[jira] [Resolved] (SPARK-45180) Remove boolean inputs for inclusive from Series.between

[ https://issues.apache.org/jira/browse/SPARK-45180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-45180. --- Fix Version/s: 4.0.0 Resolution: Fixed Issue resolved by pull request 42945

[jira] [Assigned] (SPARK-45180) Remove boolean inputs for inclusive from Series.between

[ https://issues.apache.org/jira/browse/SPARK-45180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun reassigned SPARK-45180: - Assignee: Haejoon Lee > Remove boolean inputs for inclusive from Series.between >

[jira] [Resolved] (SPARK-45078) The ArrayInsert function should make explicit casting when element type not equals derived component type

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