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.

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

HTAP #8918

Closed
1 of 4 tasks
nikvas0 opened this issue Sep 9, 2024 · 0 comments · Fixed by #8917
Closed
1 of 4 tasks

HTAP #8918

nikvas0 opened this issue Sep 9, 2024 · 0 comments · Fixed by #8917
Assignees

Comments

@nikvas0
Copy link
Collaborator

nikvas0 commented Sep 9, 2024

At the moment, transactions between OLAP, OLTP, and topics are not working due to different approaches to working with the arbiter. OLTP tables receive the arbiter from the QP and use it, but this is only possible for volatile transactions. OLAP tables ignore the KQP arbiter and use their own. Topics can't use the arbiter at all. OLTP and topics can already work together (commit without an arbiter), so the issue only affects transactions involving OLAP tables.

To solve this problem, we propose using the KQP arbiter for all OLAP table transactions. This would require the following changes:

  • Columnshards should use the arbiter selected by the QP (instead of their own).
  • Datashards should support an arbiter for non-volatile transactions (since OLAP tables cannot perform volatile transactions).
  • Topics should be able to commit using the arbiter. (Only datashard or columnshard can be arbiter.)
  • Query Processor should always choose arbiter if OLAP table is present in transaction.
@nikvas0 nikvas0 self-assigned this Sep 9, 2024
@nikvas0 nikvas0 linked a pull request Sep 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant