apache/pinot

On replicaGroupStrategyConfig Deprecation

Open

#15744 opened on May 8, 2025

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Java (4,937 stars) (1,234 forks)batch import
cleanupconfigurationgood first issue

Description

I think it was decided at some point to deprecate replicaGroupStrategyConfig.

However, right now there's no way to ensure that two tables are partitioned on a given column across the same set of instances, except using a combination of instancePartitionsMap and replicaGroupStrategyConfig.

Given this, let's make sure this is addressed before the config is removed from OSS.

Contributor guide

Tech stack
javasql
Domain
databasebackend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Apache Pinot architectureKnowledge of replica group strategy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the current usage of replicaGroupStrategyConfig in Pinot's source code, particularly in configuration classes and partitioning logic. Review the discussion in comments for proposed alternatives. Identify how instancePartitionsMap and replicaGroupStrategyConfig are jointly used to ensure co partitioning. Propose a solution to maintain that functionality after deprecation, possibly by extending instancePartitionsMap or introducing a new configuration field. Document the findings and initiate a discussion on the best path forward.