Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
As a part of the issue planed:
- Draw a time diagram of all operations: createTable(), dropTable(), table(), tables().
- Emphases of correctness work of causality tokens: tablesByIdVv.
- Reflect cross components interactions. Components: Schema manager, SQL manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now).
The task for this ticket is to make a detailed diagram of the current flow, to ease the design itself.
Definition of done:
We have detailed and clear description of table manager flows and the ticket IGNITE-18989 is enriched with details about the flaws we want to fix.
Attachments
Attachments
Issue Links
- blocks
-
IGNITE-18990 Integrate PlacementDriverManager into IgniteImpl
- Resolved
-
IGNITE-16544 Create a lock manager for causality tokens
- Open
-
IGNITE-14931 Define common error scopes and prefix
- Resolved
-
IGNITE-18989 Design table management flow (part 2)
- Resolved
- relates to
-
IGNITE-18454 Explain treading model in corresponding README.md file for TableManager
- Resolved