Skip to content

Conversation

@cloud-fan
Copy link
Contributor

What changes were proposed in this pull request?

This config was added in 3.0 and it's time to use the CORRECTED behavior by default. This is not a big deal as the CORRECTED behavior is also throwing an error, but the error message is improved to show the actual problem.

Why are the changes needed?

better error message

Does this PR introduce any user-facing change?

error message becomes different

How was this patch tested?

existing tests

Was this patch authored or co-authored using generative AI tooling?

no

@pan3793
Copy link
Member

pan3793 commented Apr 3, 2024

migration guide?

.transform(_.toUpperCase(Locale.ROOT))
.checkValues(LegacyBehaviorPolicy.values.map(_.toString))
.createWithDefault(LegacyBehaviorPolicy.EXCEPTION.toString)
.createWithDefault(LegacyBehaviorPolicy.CORRECTED.toString)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also refresh the config doc field

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes let's update the doc "The default value is EXCEPTION..."

Copy link
Member

@yaooqinn yaooqinn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, only one minor comment #45853 (comment)

Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM with the same above doc comments (migration guide and config doc field).

Also, please fix all test case failures like the following.

[info] TimestampFormatterSuite:
[info] - explicitly forbidden datetime patterns (13 milliseconds)
[info] - SPARK-31939: Fix Parsing day of year when year field pattern is missing *** FAILED *** (4 milliseconds)

@cloud-fan
Copy link
Contributor Author

closing in favor of #45859

@cloud-fan cloud-fan closed this Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants