-
Notifications
You must be signed in to change notification settings - Fork 59
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
update with accurate numeric type for common, core #612
update with accurate numeric type for common, core #612
Conversation
Signed-off-by: amberzsy <xxamber998@gmail.com>
Signed-off-by: amberzsy <xxamber998@gmail.com>
Changes AnalysisCommit SHA: f02d356 API ChangesSummary
ReportThe full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/11312514398/artifacts/2053171058 API Coverage
|
Spec Test Coverage Analysis
|
Signed-off-by: amberzsy <xxamber998@gmail.com>
I wonder whether it's a good idea to add a linter rule that warns us that a type is too generic? And then eventually turn it into an error? If you agree do open an issue please! |
agree. opened issue here |
Description
improve accuracy of numeric type for document, search api.
Issues Resolved
#596
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.