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

Compression level to not be set for default or best_compression codec #8677

Closed
sarthakaggarwal97 opened this issue Jul 13, 2023 · 0 comments · Fixed by #8737
Closed

Compression level to not be set for default or best_compression codec #8677

sarthakaggarwal97 opened this issue Jul 13, 2023 · 0 comments · Fixed by #8737
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request v2.10.0

Comments

@sarthakaggarwal97
Copy link
Contributor

Is your feature request related to a problem? Please describe.
If the users wants to update the compression level for the default/best_compression codecs then the user should not be allowed to update or set the compression level settings. The compression level settings should only be allowed for zstd/zstd_no_dict codecs.

Additional context
#7555

@sarthakaggarwal97 sarthakaggarwal97 added enhancement Enhancement or improvement to existing feature or request untriaged labels Jul 13, 2023
@sarthakaggarwal97 sarthakaggarwal97 changed the title Failure if compression level is set for default or best_compression codec Validate if compression level is set for default or best_compression codec Jul 13, 2023
@sarthakaggarwal97 sarthakaggarwal97 changed the title Validate if compression level is set for default or best_compression codec Compression level to not be set for default or best_compression codec Jul 13, 2023
@reta reta added the v2.10.0 label Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request v2.10.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants