[Feature] Add Apache Cloudberry Support

[tuhaihe]

Description

Hi there,

I’m Dianjin Wang from the Apache Cloudberry community ¹, an open-source derivative of Greenplum Database.

As you may know, Greenplum went closed-source last year. Many users are now considering Cloudberry as an open-source alternative and are actively working on migrating from Greenplum. Cloudberry is built on a newer PostgreSQL kernel (14.4 now) while maintaining strong compatibility with Greenplum.

I noticed that InLong already supports Greenplum as load node ², and I’d love to explore the possibility of adding Cloudberry support in a similar way. This would greatly benefit both projects and help former Greenplum users transition more smoothly.

I’d be happy to discuss this further with your team, and our engineers can provide technical support if needed. Please let me know if this is the right place to bring this up or if there’s a better way to proceed. Looking forward to your thoughts!

Use case

No response

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

Footnotes

1. https://github.com/apache/cloudberry ↩

2. https://inlong.apache.org/docs/data_node/load_node/greenplum ↩

[github-actions]

Hello @tuhaihe, thank you for opening your first issue in InLong 🧡 We will respond as soon as possible ⏳
If this is a bug report, please provide screenshots or error logs for us to reproduce your issue, so we can do our best to fix it.
If you have any questions in the meantime, you can also ask us on the InLong Discussions 🔍

[vernedeng]

Hi Dianjin,

Thank you very much for your attention and suggestions regarding Apache InLong. Apache InLong is very pleased to cooperate with Cloudberry to build capabilities related to data synchronization.

You can find out how to add an InLong Load Node here: https://inlong.apache.org/docs/development/extension_sort/extension_connector

[tuhaihe]

Cool! If any updates, will let you know. Thanks for your reply again!

[github-actions]

This issue is stale because it has been open for 60 days with no activity.