-
Notifications
You must be signed in to change notification settings - Fork 186
SELECT nested() cannot get sub properties #963
Comments
Hi @FreCap , thanks for reporting this issue! I was able to reproduce these cases. 1 Therefore the One option before the fix is to set the format to JSON (which are the search hits as response caught from the ES engine) rather than the default JDBC format by adding the param
2 |
Thank you @chloe-zh! I saw I could use format=json, but in this phase of dev I was trying to switch to full jdbc given how hard to read the json format for complex aggregates can be.
Thank you for keeping me up to date. |
Hi @FreCap , you can find the stack trace from es log in the node. |
Thanks @chloe-zh! As a suggestion, it'd be great having the log in the response without having to go to the machine. Having tens of machines (or not having access to them for security reasons), it becomes an extremely challenging task to complete |
Do you have any suggestion on what I could do to contribute a fix? Any, even small, guidance would be greatly appreciated |
Could you checkout the method |
How to reproduce:
1) Works as expected, contains both myNestedFieldObject and myNestedId
2) Doesn't work as expected: partial response, doesn't contain myNestedFieldObject
Response doesn't contain myNestedFieldObject
3) Doesn't work as expected: throws exception
Same for adding
myNestedField,
The text was updated successfully, but these errors were encountered: