Great to see Greenplum is using PXF. I think PXF is a very good fit for Greenplum's current architecture.
To avoid duplicate maintenance cost, my suggestion is to only maintain PXF code in one place: Greenplum. >From HAWQ side, it can be deprecated in a future release after the new framework is ready. Thanks Lei On Tue, Dec 5, 2017 at 3:02 AM, Ed Espino <[email protected]> wrote: > To the HAWQ dev community, > > I wanted to raise up an issue for discussion regarding JIRA HAWQ-786 > <https://issues.apache.org/jira/browse/HAWQ-786>. This is a proposal for a > new component/functionality (Framework to support pluggable formats and > file systems) that appears to replace that currently provided by the PXF > component. > > PXF was recently re-used in another open source project: Greenplum-DB ( > https://github.com/greenplum-db/gpdb/tree/5X_STABLE/gpAux/extensions/pxf ) > and depends on the server-side components that exist today in HAWQ’s source > tree. > > The question I have for the community is: with the possibility of PXF being > replaced by a new component in a future release of HAWQ, what should become > of the PXF code? Older releases of HAWQ (2.3.0 >) will continue to use it > but there is an outside project now depending on it. > > Does the HAWQ community want to maintain the PXF code in the HAWQ project > or if not here, where? If the GPDB community forked PXF from HAWQ would > that be ok? > > Regards, > > Ed Espino >
