bugfix: query with embedded entity producing an exception #306
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…type specific opetator is used
bahurski-ivan
changed the title
|
@igdianov any chance to merge this? |
|
@bahurski-ivan Thank you for contribution. I can also backport it into |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
lets consider an example:
we have an entity with
@Embeddedfieldembedded field contains a long value
we want to make query where embedded.longVal > 7
but unfortunately there was no way to do so, because if we do where query with:
embedded: {GT: {longVal: 7}}we will get an exception.
Unsupported field type class <className> for field <embeddedField>this PR changes schema generation for embedded and allows for such queries to be performed.
(query will look like:
embedded: {longVal: {GT: 7}})