[ 
https://issues.apache.org/jira/browse/SPARK-34276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiao Li updated SPARK-34276:
----------------------------
    Description: 
Before the release, we need to double check the unreleased/unresolved JIRAs/PRs 
of Parquet 1.11/1.12 and then decide whether we should upgrade/revert Parquet. 
At the same time, we should encourage the whole community to do the 
compatibility and performance tests for their production workloads, including 
both read and write code paths.

More details: 
[https://github.com/apache/spark/pull/26804#issuecomment-768790620]

  was:
Before the release, we need to double check the unreleased/unresolved JIRAs/PRs 
of Parquet 1.11 and then decide whether we should upgrade/revert Parquet. At 
the same time, we should encourage the whole community to do the compatibility 
and performance tests for their production workloads, including both read and 
write code paths.

More details: https://github.com/apache/spark/pull/26804#issuecomment-768790620


> Check the unreleased/unresolved JIRAs/PRs of Parquet 1.11 and 1.12
> ------------------------------------------------------------------
>
>                 Key: SPARK-34276
>                 URL: https://issues.apache.org/jira/browse/SPARK-34276
>             Project: Spark
>          Issue Type: Task
>          Components: Build, SQL
>    Affects Versions: 3.2.0
>            Reporter: Yuming Wang
>            Priority: Blocker
>
> Before the release, we need to double check the unreleased/unresolved 
> JIRAs/PRs of Parquet 1.11/1.12 and then decide whether we should 
> upgrade/revert Parquet. At the same time, we should encourage the whole 
> community to do the compatibility and performance tests for their production 
> workloads, including both read and write code paths.
> More details: 
> [https://github.com/apache/spark/pull/26804#issuecomment-768790620]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to