Skip to content

AUTO: Docs repo sync - ScalarDB #1245

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

Merged
merged 1 commit into from
May 26, 2025
Merged

AUTO: Docs repo sync - ScalarDB #1245

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/consensus-commit.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Pessimistic concurrency control (PCC), on the other hand, assumes conflicts are
The OCC protocol of ScalarDB has three phases, as the commonly used OCC protocols, each of which does the following:

* Read phase:
* ScalarDB tracks the read and write sets of transactions. ScalarDB copies every record that a transaction accesses from databases to its local workspace and stores its writes in the workspace.
* ScalarDB tracks the read and write sets of transactions. ScalarDB copies every record that a transaction accesses from databases to its local workspace and stores its writes in the local workspace.
* Validation phase:
* ScalarDB checks if the committing transaction conflicts with other transactions. ScalarDB uses backward validation; it goes to the write phase only if other transactions have not written what the transaction reads and writes, which are called read validation and write validation, respectively.
* Write phase:
Expand Down Expand Up @@ -216,7 +216,7 @@ If you take backups from multiple databases or from non-transactional databases,

In the current implementation, ScalarDB throws an exception in the following cases:

* Executing scan operations after write (Put, Insert, Update, Upsert) operations for the same record in a transaction.
* Executing scan operations after write (Put, Insert, Update, Upsert, Delete) operations for the same record in a transaction.
* Executing write (Put, Insert, Update, and Upsert) operations after Delete operations for the same record in a transaction.

## See also
Expand Down
4 changes: 2 additions & 2 deletions docs/roadmap.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ If you have a feature request or want to prioritize feature development, please

### CY2026

- ** Audit Logging**
- **Audit logging**
- Users will be able to view and manage the access logs of ScalarDB Cluster and Analytics, mainly for auditing purposes.
- **Stored procedures**
- Users will be able to define stored procedures so that they can execute a set of operations with a complex logic inside ScalarDB Cluster.
Expand All @@ -130,6 +130,6 @@ If you have a feature request or want to prioritize feature development, please
- **User-defined functions (UDFs)**
- Users will be able to define functions so that they can use functions in SQLs to express complex logic in a simpler way.
- **Addition of SQL operations for sorting**
- Users will be able to issue sorting (ORDER BY) operations in ScalarDB SQL.
- Users will be able to issue arbitrary sorting (ORDER BY) operations in ScalarDB SQL for multiple or non-JDBC databases. (Currently, ScalarDB can issue sorting operations using clustering keys or arbitrary sorting operations for single JDBC databases.)
- **Addition of more data types**
- Users will be able to use complex data types, such as JSON.