Hello everyone
I suggest adding a roadmap to better plan the functionality of PXF. In the issue https://github.com/apache/cloudberry-pxf/issues/69, we discussed a roadmap for PXF. What are some better suggestions? We hope to receive more suggestions to improve the PXF ecosystem. 1. Community, Marketing, and Branding Suggestions - Documentation refresh and branding alignment: It is recommended to update existing documentation by replacing legacy Greenplum-related branding with Apache Cloudberry–aligned terminology to avoid user confusion. - Documentation integration with the Cloudberry website: Ensure PXF documentation is properly integrated or cross-referenced with the Cloudberry official website, making it easier for users to discover, understand, and adopt PXF as part of the broader ecosystem. - Release alignment and packaging support: Align the PXF release cadence with Cloudberry’s release cycle where possible, and provide standard distribution formats such as .deb, .rpm, and ASF-compliant source release artifacts. 2. Current Maintenance Scope - Add Java 17 support. - Continue updating dependencies to address security warnings generated by GitHub (although most issues are nearly impossible to exploit, policy recommends fixing them anyway). 3. Potential Features Under Consideration - Upgrade Hadoop-related libraries to v3.x. - Use TestContainers to replace run-test.sh (pure Java implementation, with no impact on end users). - IMPORT FOREIGN SCHEMA functionality (not yet tested with pxf_fdw). 4. Future Possible Directions - PXF parallel data loading. - Lakehouse examples (Iceberg support). - PXF pushdown capabilities enhancement.
