Don't validate decimal precision in ArrayData (#2637) #2873
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Part of #2637
Rationale for this change
As of #2857 we no longer validate precision, we should not do this as part of full ArrayData validation for consistency
What changes are included in this PR?
Disables precision validation as part of ArrayData::validate_values
Are there any user-facing changes?
Sort of, data that would previously fail to validate may now pass. However, we were so inconsistent about applying validation in the first place #2387 I don't imagine anyone could have relied on this.