Remove legacy Greenplum support from cloudberry-backup
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by inventorying the source code, build and configuration files, runtime checks, documentation, tests, and CI workflows mentioned in the scope. Done means Greenplum-specific logic and compatibility references are removed, Cloudberry behavior remains supported, and the affected tests and workflows are updated.
Written by the indexing model from the issue text.
Description
Background
The cloudberry-backup project was originally derived from Greenplum backup tooling and still contains legacy code paths, configurations, and compatibility logic intended to support Greenplum Database environments.
Since Apache Cloudberry has evolved as an independent project with its own architecture, release cycle, and compatibility guarantees, continuing to maintain legacy Greenplum support introduces unnecessary complexity and maintenance burden.
Motivation
Removing legacy Greenplum support will provide several benefits:
- Simplify the codebase and reduce maintenance overhead
- Improve code clarity and long-term maintainability
- Align the project strictly with Apache Cloudberry’s architecture and roadmap
- Reduce testing and validation scope
- Avoid confusion about supported platforms
The cloudberry-backup project should be focused solely on serving Apache Cloudberry users.
Scope of Changes
Expected areas of modification include:
- Source code cleanup and removal of Greenplum-specific logic
- Update build, configuration, and runtime checks
- Documentation updates
- Test suite cleanup
- CI workflow adjustments if applicable
Compatibility Impact
This change will be backward-incompatible for Greenplum users. However, since this repository is now part of the Apache Cloudberry ecosystem, focusing exclusively on Cloudberry is consistent with project goals.
- Dominant language
- Go
- Stars
- 18
- Forks
- 22
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/cloudberry-backup
-
apache/cloudberry-backup#115 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/cloudberry-backup#103 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/cloudberry-backup#101 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
apache/cloudberry-backup#80 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
apache/cloudberry-backup#65 · 11 comments ·
All issues in apache/cloudberry-backup
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
acceptance-tests phase-coding schema-coverage testing triaged
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100