Bugfix patch #544
Merged
Bugfix patch #544
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
…d-and-gql-query-doesnt-contain-query-name fix(#532): NPE when GQL query is sent without a name and tracing is enabled
…r work with the multiline text inside
…an better work with the multiline text inside" This reverts commit 9eb443e.
… work with the multiline text inside
…n-json-layout fix(#534): log exception with log message so that consumers can better work with the multiline text inside
…es into account Equal date times: - `2024-04-24T11:07:11.677467736Z` - `2024-04-24T13:07:11.677467736+02:00` were considered different. Also, the filter index didn't take string collations into account, so less than & greater than didn't work properly for strings containing national characters. The fix changed the format of the stored data, so I had to include a backward compatible deserializer so that existing data is loaded correctly. When the data is saved again, it has the correct new format. The old format should be automatically removed by compaction.
…version-on-the-way-from-the-client-to-the-server fix (#536): Invalid OffsetDateTime comparison taking offset difference into an account
When UserFilterFormula was not part of the computational tree, the facet impact computation didn't work well.
…-difference-when-userfilter-is-used fix(#537): Incorrect facet statistics difference when userFilter is used
There's a transactional boolean `dirty` in many places in transactional data structures, but it's not taken into account in the `io.evitadb.core.transaction.memory.TransactionalLayerProducer#createCopyWithMergedTransactionalMemory` method, which is called when a new state is created. If we had taken advantage of this flag and just returned "this" reference in cases where it's not dirty, we could save a lot of memory allocations. If nothing has changed, we can reuse the exact same instance of the object for the next generation.
…changes-in-indexes-occur refactor(#542): Limit allocations when no changes in indexes occur
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.