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

feat(shannon): add a consistence type system variable #245

Open
ShannonBase opened this issue Sep 13, 2024 · 0 comments
Open

feat(shannon): add a consistence type system variable #245

ShannonBase opened this issue Sep 13, 2024 · 0 comments
Assignees
Labels
feature it will be implemented as a new feature

Comments

@ShannonBase
Copy link
Contributor

ShannonBase commented Sep 13, 2024

Summary

In ShannonBase, we proivde two types sync ways:(1) strong consitence; (2) async consitence; Different consistent type has different implementation.

1: strong consistence:To monitor DML operations in innodb layer, and apply the changes in sync. This makes performance impact.
2: Async consistence: To use redo log a immediate media to shipp all changes to rapid engine, and parse these redos, then apply those changes. This's friendly to distributed framework, especially on cloud evn.

In single node mode, strong is recommended, but, on cloud, async is a good choice.

Oracle In memory column store, about re-population and query

During automatic repopulation, traditional access mechanisms are available. Data is always accessible from the buffer cache or disk. Additionally, the IM column store is always transactionally consistent with the data on disk. No matter where the query accesses the data, the database always returns consistent results.

@ShannonBase ShannonBase added the feature it will be implemented as a new feature label Sep 13, 2024
@ShannonBase ShannonBase changed the title feat(shannon): add a system variable to indicate which consitence type we use feat(shannon): add a consistence type system variable Sep 13, 2024
@ShannonBase ShannonBase self-assigned this Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature it will be implemented as a new feature
Projects
None yet
Development

No branches or pull requests

1 participant