Release 2024.12
#765
Merged
Release 2024.12
#765
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
…orrect implementation, removed option to specify custom allowed origins
…ess-apis-when-custom-allowed-origins-are-set fix(#702): reimplemented CORS filter and preflight handler for more correct implementation, removed option to specify custom allowed origins
refactor(#633): remove old unused evitaLab REST API
# Conflicts: # .idea/compiler.xml # evita_api/src/main/java/io/evitadb/api/requestResponse/EvitaRequest.java # evita_engine/src/main/java/io/evitadb/core/query/QueryPlanBuilder.java # evita_external_api/evita_external_api_observability/src/main/java/io/evitadb/externalApi/observability/metric/PrometheusMetricsHttpService.java
And also added additional tests. It seems that in certain cases the requirements were not collected correctly.
Update evitaLab to v2024.3.0
# Conflicts: # evita_external_api/evita_external_api_observability/src/main/java/io/evitadb/externalApi/observability/metric/PrometheusMetricsHttpService.java
…ints feat(#677): in scope container constraints fixes
…non managed referenced groups
…unctiondisjunctionnegation-on-non-managed-referenced-groups fix(#755): Cannot use facetGroup conjunction/disjunction/negation on …
Various fixes related to scope being ignored in complex queries.
…es-in-changelog ci(release-notes): better communicate changes in release notes. Refs: #758
Reflected references were allowed originally only in the very same scope. In reality we need those across scopes - if the reference schemas are indexed in both of scopes. This allows us to look up for entities by reference having / entity having in multiple scopes at once.
Updated documentation.
Update evitaLab to v2024.4.2
…request of different scope
…e filter
When this filter is used:
```
filterBy: {
inScope: {scope: LIVE, filtering: {attributeVariantEquals: true}}
}
```
And the scope doesn't match the superset would be used. But that needs to respect the scope of the original entity.
…e filter
When this filter is used:
```
filterBy: {
inScope: {scope: LIVE, filtering: {attributeVariantEquals: true}}
}
```
And the scope doesn't match the superset would be used. But that needs to respect the scope of the original entity.
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.
No description provided.