test: use NTS keyspace in PreparedStatementTest#944
Conversation
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis change modifies a single test in PreparedStatementTest.java. The CQL statement used to create the case-sensitive "Test" keyspace within the should_set_routing_key_on_case_sensitive_keyspace_and_table test now specifies NetworkTopologyStrategy with a datacenter1 setting, replacing the previous SimpleStrategy configuration with a replication_factor. No other test logic or public entities are affected. Compact metadata:
Related issues: None specified Related PRs: None specified Suggested labels: test, low-risk Suggested reviewers: None specified Poem: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
d0cfe22 to
7b18eeb
Compare
Scylla 2026.2.0 rejects SimpleStrategy when tablet replication is enabled. A few short integration tests still created keyspaces with SimpleStrategy, which causes the Scylla IT matrix to fail before the actual test assertions run.
This switches those test keyspaces to NetworkTopologyStrategy with datacenter1 RF=1, matching the 3.x test-suite cleanup already done for other Scylla integration tests.
Observed failures:
Tested: