fix(#392): Cannot fetch bodies for multiple entities from multiple collections #394
Conversation
This file contains 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
…re each entity is from different entity collection
…llections
When using multiple globally unique identifiers in single query to fetch entities where each entity is from different collection AND entity body is wanted, like so:
```
query(
filterBy(
attributeInSet("url", "/en/macbook-pro-13-2022", "/en/cell-phones"),
entityLocaleEquals("en")
),
require(
entityFetch(
attributeContent("code")
)
)
)
```
evitaDB returns error
```
Entity `Product` with primary key `63049` cannot be enriched because it has been already removed.
```
If both URLs would target the same collection, both entities would be returned with their bodies as expected.
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.
When using multiple globally unique identifiers in single query to fetch entities where each entity is from different collection AND entity body is wanted, like so:
evitaDB returns error
If both URLs would target the same collection, both entities would be returned with their bodies as expected.