-
Notifications
You must be signed in to change notification settings - Fork 126
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
[BUG] Missing aggs
property for search.
#977
Comments
If the server still supports it then yes. Please do contribute! |
Shall we close this issue @Xtansia ? |
@xavianaxw Should likely leave the issue open until the changed spec actually gets pulled in via the next code generation run. (cc @nhtruong) |
@xavianaxw the codegen is having trouble handling the edge case of nested oneOf within allOf. This will have to be treated as an edge case since the codegen does not assume that all sub-schemas of oneOf are of the same type (i.e. object in this case), but we must have a guard to detect if they are all objects. so it can collect all properties within oneOf and put them in the same object. Note that there's no 1 to 1 translation from JSON Schemas to TS types, so the best-effort in this case is an object with all properties defined within |
What is the bug?
Related to #956 , should
aggs
be supported in nested aggregations?How can one reproduce the bug?
What is the expected behavior?
For
aggs
to be supportedDo you have any screenshots?
Additional question
Considering the big release of opensearch-project v3 was revolved around the opensearch API specification generator, should it only support
aggregations
moving forward? oraggs
is expected to continue working?The text was updated successfully, but these errors were encountered: