Skip to content

CASSANDRA-21642 Consider the introduction of flush_compression CQL table parameter - #5100

Draft
smiklosovic wants to merge 3 commits into
apache:trunkfrom
smiklosovic:CASSANDRA-21642
Draft

CASSANDRA-21642 Consider the introduction of flush_compression CQL table parameter#5100
smiklosovic wants to merge 3 commits into
apache:trunkfrom
smiklosovic:CASSANDRA-21642

Conversation

@smiklosovic

Copy link
Copy Markdown
Contributor

Thanks for sending a pull request! Here are some tips if you're new here:

  • Ensure you have added or run the appropriate tests for your PR.
  • Be sure to keep the PR description updated to reflect all changes.
  • Write your PR title to summarize what this PR proposes.
  • If possible, provide a concise example to reproduce the issue for a faster review.
  • Read our contributor guidelines
  • If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:

<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

if this_opt in ('read_repair'):
return [Hint('<\'none\'|\'blocking\'>')]
if this_opt == 'flush_compression':
return ["'auto'", "'none'", "'fast'", "'table'"]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we want to hard code this on the parser.g?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

why not?

public boolean compatibleWith(ClusterMetadata metadata)
{
return metadata.directory.commonSerializationVersion.isAtLeast(Version.V0);
return metadata.directory.commonSerializationVersion.isAtLeast(attrs.minimumSerializationVersion());

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is this change related?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes

// entirely as the "compression" member field is provided outside the scope of this class.
// It may make sense in the future to refactor the ownership of the compression flag so that
// We can bypass the CompressedSequentialWriter in this case entirely.
case auto:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we need a case for "fast"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yeah, I think we need that, also to be aligned with what is in yaml. fast is in this case and also in auto logic in resolveCompressionParams

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