Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A2C48200D73 for ; Tue, 5 Dec 2017 15:10:25 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A151F160C0A; Tue, 5 Dec 2017 14:10:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C87FC160C1B for ; Tue, 5 Dec 2017 15:10:24 +0100 (CET) Received: (qmail 30596 invoked by uid 500); 5 Dec 2017 14:10:23 -0000 Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list dev@hawq.incubator.apache.org Received: (qmail 30211 invoked by uid 99); 5 Dec 2017 14:10:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2017 14:10:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C233CC01B7; Tue, 5 Dec 2017 14:10:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id fx0KqiaqtAgJ; Tue, 5 Dec 2017 14:10:17 +0000 (UTC) Received: from mail-ot0-f175.google.com (mail-ot0-f175.google.com [74.125.82.175]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 6271C5F256; Tue, 5 Dec 2017 14:10:17 +0000 (UTC) Received: by mail-ot0-f175.google.com with SMTP id p3so309940oti.5; Tue, 05 Dec 2017 06:10:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=PxQy8FwHvVjj7Yyo4SWtZTuNNmuaXfM5z1UJnopBiws=; b=eb14pNi+m3ttOhZC28O3N+Z0fOJV95D+IXCQ8GU7fkxy199ANUpdjFQbwoKyqOWvLr i2gcp2hEo14SHMn+nfAK/WxwMyQQ/PkfaTtlRo2t0NUBByjt7TqSlbBq4O0XqJQvN5Vu l996uUlx+q2QjQNTXzDRtoyF1c+V0j39kU2nS3O2FPLgANK18gTampoY/++QLKXqWZaI oUynhaZFqNL5PijSaSVG0ZJOvHeP4yzBOM7kRxs/caZDLIOJe7NDPXN8SWBXf0E5S6PI EywiZRG48biOnzHlpvB+QKx9KaLzbE8mve9bPfcvj678rlIGyXcs14SdIxHE3SvCESli ZOsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=PxQy8FwHvVjj7Yyo4SWtZTuNNmuaXfM5z1UJnopBiws=; b=DIAH7U+SSoetiSgCgLfkgGTzKMo6SLd7kY7TgbX5uTEXr5Lr+fBH8OdtEHJAGP0Koh bizLnbhnX1SFub9dNjtBBYJky7aiefMnaT0xtbBqky2yITRz3zaGd6x34Csfby8+7kab Q4dyZFm6uv7Le5Pnaj5ft3zaw1qsjE3NRcfDVNGpAluGgL2/MZhI4FEeJOERHAdtlhOx zrIE78AZV0R5bV9ShNNTDn3r3/IgkYvIrSCnfqFWRogWzMdki1SvD/cen/2EX51tB0/h K807kZhbQcGV3/4HnMoe4pTygwHE/sUBUNH6/u6mmxJyvPkaFKoYwbPVB0VjCdd4Phvc m7pA== X-Gm-Message-State: AJaThX5PrxbGZBm6cKizxtnIt1ecT32lUtp+L7933436X7ZA1o0/bOti FMkf5o2HmFs1cR5BVnBHvZc0xwtV X-Google-Smtp-Source: AGs4zMZE1X/xkjFbdSsID5jDs+d5bVJTKVSWUTD6Uiqrb8QsaAj0HkMGyxrDMKgbhOJa6BDr6rlEmw== X-Received: by 10.157.26.35 with SMTP id a32mr19539484ote.210.1512483011171; Tue, 05 Dec 2017 06:10:11 -0800 (PST) Received: from mail.outlook.com ([13.89.224.24]) by smtp.gmail.com with ESMTPSA id r62sm91530oih.13.2017.12.05.06.10.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Dec 2017 06:10:10 -0800 (PST) Date: Tue, 5 Dec 2017 14:10:09 +0000 (UTC) From: chang.lei.cn@gmail.com To: dev@hawq.incubator.apache.org, Cc: user Message-ID: <5590DB2387FAB413.678770E1-ED29-40CE-902F-61C9EED1FECC@mail.outlook.com> In-Reply-To: References: Subject: Re: Questions for HAWQ dev community: Pluggable storage formats and files systems vs. PXF MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4243_1186701515.1512483009495" X-Mailer: Outlook for iOS and Android archived-at: Tue, 05 Dec 2017 14:10:25 -0000 ------=_Part_4243_1186701515.1512483009495 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =09 =09=09 =09=09 =09 =09=09Mike, =C2=A0the new framework will include all the plugins for extern= al data.=20 ThanksLei =09=09 =09=09 =09=09CheersLei =09 On Tue, Dec 5, 2017 at 5:30 PM +0800, "Michael Pearce" wrote: Lei, I would disagree. The Jira / feature doesn=E2=80=99t cater for integration = with other Hadoop components or other sources such as HBase etc, it simply = seems to cover storage of internal data. As such I wouldn=E2=80=99t like to see a component maintained in apache for= Apache Hawq, moved out of Apache ownership and governance. It should remain whilst still core to HAWQ in this ASF project. Regards Mike On 05/12/2017, 01:19, "Lei Chang" wrote: 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 wrote: > To the HAWQ dev community, > > I wanted to raise up an issue for discussion regarding JIRA HAWQ-786 > . This is a proposal for a > new component/functionality (Framework to support pluggable formats a= nd > 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=E2= =80=99s 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 us= e it > but there is an outside project now depending on it. > > Does the HAWQ community want to maintain the PXF code in the HAWQ pro= ject > or if not here, where? If the GPDB community forked PXF from HAWQ wou= ld > that be ok? > > Regards, > > Ed Espino > The information contained in this email is strictly confidential and for th= e use of the addressee only, unless otherwise indicated. If you are not the= intended recipient, please do not read, copy, use or disclose to others th= is message or any attachment. Please also notify the sender by replying to = this email or by telephone (+44(020 7896 0011) and then delete the email an= d any copies of it. Opinions, conclusion (etc) that do not relate to the of= ficial business of this company shall be understood as neither given nor en= dorsed by it. IG is a trading name of IG Markets Limited (a company registe= red in England and Wales, company number 04008957) and IG Index Limited (a = company registered in England and Wales, company number 01190902). Register= ed address at Cannon Bridge House, 25 Dowgate Hill, London EC4R 2YA. Both I= G Markets Limited (register number 195355) and IG Index Limited (register n= umber 114059) are authorised and regulated by the Financial Conduct Authori= ty. ------=_Part_4243_1186701515.1512483009495--