Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEA] Spark3.1.0 test spark.sql.legacy.parquet.int96RebaseModeInRead #1135

Closed
tgravescs opened this issue Nov 17, 2020 · 2 comments · Fixed by #3330 or #3643
Closed

[FEA] Spark3.1.0 test spark.sql.legacy.parquet.int96RebaseModeInRead #1135

tgravescs opened this issue Nov 17, 2020 · 2 comments · Fixed by #3330 or #3643
Assignees
Labels
P1 Nice to have for release Spark 3.1+ Bugs only related to Spark 3.1 or higher task Work required that improves the product but is not user facing

Comments

@tgravescs
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Spark 3.1.0 added some configs for int96 rebase spark.sql.legacy.parquet.int96RebaseModeInRead and spark.sql.legacy.parquet.int96RebaseModeInWrite. Make sure we support and test accordingly

@tgravescs tgravescs added feature request New feature or request P1 Nice to have for release Spark 3.1+ Bugs only related to Spark 3.1 or higher labels Nov 17, 2020
@jlowe
Copy link
Member

jlowe commented Aug 11, 2021

I think we need to support this ASAP, since we try to honor spark.sql.legacy.parquet.datetimeRebaseModeInRead and spark.sql.legacy.parquet.datetimeRebaseModeInWrite and these new INT96 configs override the old datetime versions when using INT96 timestamps.

@sameerz sameerz added task Work required that improves the product but is not user facing and removed feature request New feature or request labels Aug 13, 2021
@sameerz sameerz added this to the Aug 16 - Aug 27 milestone Aug 26, 2021
@sameerz sameerz linked a pull request Aug 28, 2021 that will close this issue
@tgravescs tgravescs reopened this Sep 23, 2021
@tgravescs
Copy link
Collaborator Author

reopen because reverted due to build failures and not up to date with latest shim changes:
#3627

tgravescs pushed a commit to tgravescs/spark-rapids that referenced this issue Nov 30, 2023
…IDIA#1135)

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Nice to have for release Spark 3.1+ Bugs only related to Spark 3.1 or higher task Work required that improves the product but is not user facing
Projects
None yet
4 participants