Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7202317D2F for ; Wed, 1 Apr 2015 18:22:34 +0000 (UTC) Received: (qmail 73063 invoked by uid 500); 1 Apr 2015 18:22:34 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 72992 invoked by uid 500); 1 Apr 2015 18:22:34 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 72981 invoked by uid 99); 1 Apr 2015 18:22:34 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2015 18:22:34 +0000 Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C25101A012D for ; Wed, 1 Apr 2015 18:22:33 +0000 (UTC) Received: by igcau2 with SMTP id au2so55997626igc.0 for ; Wed, 01 Apr 2015 11:22:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.159.84 with SMTP id i81mr26219671ioe.32.1427912552934; Wed, 01 Apr 2015 11:22:32 -0700 (PDT) Received: by 10.107.132.85 with HTTP; Wed, 1 Apr 2015 11:22:32 -0700 (PDT) In-Reply-To: <551C2690.6050201@gmail.com> References: <551C2690.6050201@gmail.com> Date: Wed, 1 Apr 2015 11:22:32 -0700 Message-ID: Subject: Re: ORC separate project From: "Owen O'Malley" To: "dev@hive.apache.org" Content-Type: multipart/related; boundary=001a1140b8ec7d16250512adcce8 --001a1140b8ec7d16250512adcce8 Content-Type: multipart/alternative; boundary=001a1140b8ec7d16220512adcce7 --001a1140b8ec7d16220512adcce7 Content-Type: text/plain; charset=UTF-8 On Wed, Apr 1, 2015 at 10:10 AM, Alan Gates wrote: > > > Carl Steinbach > April 1, 2015 at 0:01 > > Hi Owen, > > I think you're referring to the following questions I asked last week on > the PMC mailing list: > > 1) How much if any of the code for vectorization/sargs/ACID will migrate > over to the new ORC project. > > 2) Will Hive contributors encounter situations where they are required to > make changes to ORC in order to complete work on projects related to > vectorization/sargs/ACID or other Hive features? > > What I'd like to see here is well defined interfaces in Hive so that any > storage format that wants can implement them. Hopefully that means things > like interfaces and utility classes for acid, sargs, and vectorization move > into this new Hive module storage-api. Then Orc, Parquet, etc. can depend > on this module without needing to pull in all of Hive. > > Then Hive contributors would only be forced to make changes in Orc when > they want to implement something in Orc. > Agreed. The goal of the new module keep a clean separation between the code for ORC and Hive so that vectorization, sargs, and acid are kept in Hive and are not moved to or duplicated in the ORC project. .. Owen --001a1140b8ec7d16220512adcce7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Apr 1, 2015 at 10:10 AM, Alan Gates <alanfgates@gmail.com> wrote:
=20 April 1, 2015 at= =20 0:01
= 
Hi Owen,

I think you're referring to the following questions I asked last week o=
n
the PMC mailing list:

1) How much if any of the code for vectorization/sargs/ACID will migrate
over to the new ORC project.

2) Will Hive contributors encounter situations where they are required to
make changes to ORC in order to complete work on projects related to
vectorization/sargs/ACID or other Hive features?
What I'd like to see here is well defined interfaces in Hive so that an= y storage format that wants can implement them.=C2=A0 Hopefully that means= =20 things like interfaces and utility classes for acid, sargs, and=20 vectorization move into this new Hive module storage-api.=C2=A0 Then Orc,= =20 Parquet, etc. can depend on this module without needing to pull in all=20 of Hive.

Then Hive contributors would only be forced to make changes in Orc when=20 they want to implement something in Orc.

Agreed. The goal of the new module keep a clean separation between = the code for ORC and Hive so that vectorization, sargs, and acid are kept i= n Hive and are not moved to or duplicated in the ORC project.
.. Owen
--001a1140b8ec7d16220512adcce7-- --001a1140b8ec7d16250512adcce8--