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

Backport to branch(3) : Add cross-partition scan options #1324

Merged
merged 1 commit into from
Nov 28, 2023
Merged

Conversation

jnmt
Copy link
Contributor

@jnmt jnmt commented Nov 24, 2023

Backport of #1294

Not just fixing the conflicts, but I changed the default value of the cross-partition scan option to keep backward compatibility in v3.x. Please take a quick look when you get a chance.

@@ -24,6 +24,9 @@ public static Properties getProperties(@SuppressWarnings("unused") String testNa
props.setProperty(DatabaseConfig.CONTACT_POINTS, contactPoints);
props.setProperty(DatabaseConfig.USERNAME, username);
props.setProperty(DatabaseConfig.PASSWORD, password);
props.setProperty(DatabaseConfig.CROSS_PARTITION_SCAN, "true");
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to true in v3.x.

@@ -0,0 +1,6 @@
package com.scalar.db.storage.cassandra;

public class CassandraConfig {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In v3.x, there isn't CassandraConfig, but I added it to provide STORAGE_NAME, as the same as other storages.

Copy link
Collaborator

@brfrn169 brfrn169 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you!

Copy link
Contributor

@feeblefakie feeblefakie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you!

@brfrn169 brfrn169 merged commit 42d60df into 3 Nov 28, 2023
23 checks passed
@brfrn169 brfrn169 deleted the 3-pull-1294 branch November 28, 2023 05:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants