yugabyte/yugabyte-db

Backend compression setting per table / keyspace / yedis instance configuration

Open

#1,413 opened on May 20, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C (8,229 stars) (1,003 forks)batch import
area/docdbcommunity/requestgood first issuekind/enhancementpriority/medium

Description

Jira Link: DB-1623 I would like to store some parts of my data as images / zip (media content) possible to remove the compression at backend so i can save the extra cpu processing? per table / keyspace / yedis instance.

For yedis is better. mostly for media content will just get set / hset / hget original jpg

Contributor guide

Tech stack
csqlredis
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with C programmingUnderstanding of database storage enginesKnowledge of compression
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the current compression implementation in YugabyteDB, focusing on the storage engine. Look for existing table level configurations for other parameters in the codebase. Explore the YEDIS implementation to understand how per instance settings could be added. Check the linked Jira issue for additional requirements.