Project

General

Profile

Actions
Copy link

Feature #47422

closed

compressor: Make Zstandard compression level a configurable option

Added by Bryan Stillwell over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus, octopus
Reviewed:
Affected Versions:
Pull request ID:
33790

Description

I would like to get this PR which was merged to master earlier this year backported to Nautilus and Octopus:

https://github.com/ceph/ceph/pull/33790

Related issues 3 (0 open — 3 closed)

Related to RADOS - Feature #43377: Make Zstandard compression level a configurable optionResolvedBryan Stillwell

Actions
Copied to Ceph - Backport #47424: octopus: compressor: Make Zstandard compression level a configurable optionResolvedActions
Copied to Ceph - Backport #47425: nautilus: compressor: Make Zstandard compression level a configurable optionResolvedActions
Actions
Copy link
 #1

Updated by Bryan Stillwell over 3 years ago

This change is adds a similar option that already exists for zlib to control the compression level zstd uses. I feel like it should be backported to nautilus/octopus because not only would my team benefit from being able to use it after the next release, but others will as well.

Actions
Copy link
 #2

Updated by Neha Ojha over 3 years ago

  • Status changed from New to Pending Backport
  • Pull request ID set to 33790
Actions
Copy link
 #3

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47424: octopus: compressor: Make Zstandard compression level a configurable option added
Actions
Copy link
 #4

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47425: nautilus: compressor: Make Zstandard compression level a configurable option added
Actions
Copy link
 #5

Updated by Sebastian Wagner over 3 years ago

  • Related to Feature #43377: Make Zstandard compression level a configurable option added
Actions
Copy link
 #6

Updated by Nathan Cutler over 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF