-
Notifications
You must be signed in to change notification settings - Fork 867
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
Do we need to public the MAX_DECIMAL_FOR_LARGER_PRECISION
and MIN_DECIMAL_FOR_EACH_PRECISION
#2343
Comments
But in the preview release, we have exposed the |
Hi @liukun4515 Are you suggesting that the constants such as For anyone else who is interested, here is a link to the constants in question for your reference: |
Yes, we don't need to expose these two constant variables. |
it might be worth creating a PR with any proposed changes you have in mind so we can evaluate them. Also, given we have been cranking out new major semver releases every 2 weeks I think it is ok if the API changes frequently in some of the areas that have more active churn and feature maturation like Decimal |
👌 |
I think it is a minor change. Although these |
I tried to make these private in #2711 (comment) but they are currently in use by DataFusion. As more decimal logic gets moved to arrow-rs we may be able to remove these, but currently they are needed |
Which part is this question about
FYI #2320
For #2320, I will change the
MIN
andMAX
array to bytes array. This will make a API break changes.@viirya @alamb
Describe your question
Additional context
The text was updated successfully, but these errors were encountered: