+1 to going the YAML route w/ thisAlong with CASSANDRA-18112, and when defaulted to legacy 2i, the following process should be possible:1.) legacy 2i exists and serves queries2.) SAI index is added and begins building3.) SAI index build completes4.) use 18112 to exclude legacy 2i in test queries (a
Tossing out an idea without any knowledge of implementation details - could
we use the SAI index when a partition key is provided, and legacy when none
is?
On Thu, Feb 6, 2025 at 1:59 PM Benedict wrote:
> Oof, if nothing else it sounds like a bug that we prefer an unbuilt index
> over a built on
Oof, if nothing else it sounds like a bug that we prefer an unbuilt index over a built one when there’s a choice.It also sounds like a bug for SAI to self report as the best index without any consideration, but perhaps that is harder to address.On 6 Feb 2025, at 21:15, C. Scott Andreas wrote:Pref
Preference for a yaml property and MBean. Briefly:– All other secondary index config is defined in yaml.– System properties are more cumbersome to manage in that they’re less structured and commingle JVM configuration with database configuration.– We need an MBean hot property so users can flip to
System property works for me, even if I have to leave the default alone in
5.0.x
On Thu, Feb 6, 2025 at 1:34 PM Jeremiah Jordan
wrote:
> Rather than changing the default, I would be +1 to making a system
> property so that an operator who knows what they are doing could change
> it. A little he
Rather than changing the default, I would be +1 to making a system
property so that an operator who knows what they are doing could change
it. A little hesitant of just changing it outright in a patch release.
On Feb 6, 2025 at 1:10:28 PM, Caleb Rackliffe
wrote:
> Hey everyone!
>
> I'll keep
