Skip to content

Conversation

@pauloricardomg
Copy link
Contributor

No description provided.

Copy link
Contributor

Choose a reason for hiding this comment

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

To be explicit, this will be printed like: "Adding snapshots: ["snapshot1", "snapshot2","snapshot3"]" ?
I think there is some joining collector which just separates it by commas and leaves brackets. I consider it to be just nicer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated. New output:

DEBUG [main] 2022-05-12 17:08:30,773 SnapshotManager.java:119 - Adding snapshots: ks:tbl:c7483545-103a-493e-b66e-6d96e60d3878:expired, ks:tbl:984bd8f1-35fd-44d7-b69b-52422614e25f:non-expired, ks:tbl:deff9907-495b-4497-8275-ffdfdfc3ad7b:non-expiring.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ehm ... should not it be the name of the snapshot rather than keyspace:table:id? I mean, we are adding snapshots, I do not see the names of these snapshots or am I getting something wrong?

Copy link
Contributor

Choose a reason for hiding this comment

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

why rf 2? dont we have just one node? Also, can no you use that distributed keyspace which is created already?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

why rf 2?

copied over from previous tests - fixed all tests to use RF=1 on 007958f.

Also, can no you use that distributed keyspace which is created already?

This whole class uses this format and fixing would be out of the scope of this ticket. Is it fine if we refactor this later?

Copy link
Contributor

@smiklosovic smiklosovic May 10, 2022

Choose a reason for hiding this comment

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

same, rf = 2, why not 1 and why dont we use default keyspace.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed to use rf=1 on 007958f

@VisibleForTesting
protected synchronized void addSnapshots(Collection<TableSnapshot> snapshots)
{
logger.debug("Adding snapshots: {}.", Joiner.on(", ").join(snapshots.stream().map(s -> s.getId()).collect(Collectors.toList())));
Copy link
Contributor

Choose a reason for hiding this comment

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

this looks better but what I see is that we have "keyspace:table:id" rather than name of that snapshot (snapshot tag).

Copy link
Contributor

@smiklosovic smiklosovic May 13, 2022

Choose a reason for hiding this comment

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

Ahaaaa I get this, so after "id" there is the snapshot tag, the whole name has four components, ks:tb:id:tag. I overlooked the last part. All good.

blambov pushed a commit to blambov/cassandra that referenced this pull request Mar 28, 2025
…ead of the query analyzer (apache#1615)

Fix `RowFilter.AnalyzableExpression#numFilteredValues`, which is
used by the `query_filters` guardrail, to use the query analyzer, instead
of the index analyzer. That prevents wrong triggerings of the guardrail.
michaelsembwever pushed a commit to thelastpickle/cassandra that referenced this pull request Jan 7, 2026
…ead of the query analyzer (apache#1615)

Fix `RowFilter.AnalyzableExpression#numFilteredValues`, which is
used by the `query_filters` guardrail, to use the query analyzer, instead
of the index analyzer. That prevents wrong triggerings of the guardrail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants