Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cache inconsistency #37

Open
novoj opened this issue Mar 2, 2023 · 0 comments
Open

Cache inconsistency #37

novoj opened this issue Mar 2, 2023 · 0 comments
Assignees
@novoj
Labels
bug Something isn't working
Milestone
Beta

Comments

@novoj
Copy link
Collaborator

novoj commented Mar 2, 2023

During manual testing of evitaDB we've run into scenarios where evitaDB returned inconsistent results. The problem disappeared when the cache was turned off, which means there is a problem in the cache key calculation. We need to track down this problem.
@novoj novoj added the bug Something isn't working label Mar 2, 2023
@novoj novoj added this to the Alpha milestone Mar 2, 2023
@novoj novoj self-assigned this Mar 2, 2023
@novoj novoj modified the milestones: Alpha, Beta Apr 26, 2024
novoj added a commit that referenced this issue Jun 14, 2024
@novoj
feat(#37): Cache inconsistency
3d79f7b 
Refactored work with QueryContext dividing it into two - QueryPlanningContext and QueryExecutionContext. The latter is unique per (isolated for) QueryPlan execution. This lead to simplification of the QueryPlanning and avoiding issues with multiple plans execution and result comparison for debug requirements.
novoj added a commit that referenced this issue Jun 19, 2024
@novoj
feat(#37): Cache inconsistency
f139a60 
Refactored work with QueryContext dividing it into two - QueryPlanningContext and QueryExecutionContext. The latter is unique per (isolated for) QueryPlan execution. This lead to simplification of the QueryPlanning and avoiding issues with multiple plans execution and result comparison for debug requirements.

The initialization of the formulas, sorters and computers is also changed and most of the initialization logic is moved to constructors. The only exception to this is calculation of costs which may rely on execution context and the fact whether the entities are prefetched.
novoj added a commit that referenced this issue Jun 19, 2024
@novoj
feat(#37): merge #41 and #37 branches
4ed014f
@novoj novoj mentioned this issue Jun 24, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@novoj novoj

Labels
bug Something isn't working
Projects
None yet
Milestone
Beta
Development

No branches or pull requests
1 participant
@novoj