Mailing-List: contact dev-help@tajo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.apache.org
Received-SPF: pass (nike.apache.org: domain of atri.jiit@gmail.com designates
 209.85.160.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAM=XDd-gu3_ZuC-TTuwaO3dU=FdQvjKGGAJOMxGJtG6TEtdSbA@mail.gmail.com>
References: 
 <CAM=XDd-gu3_ZuC-TTuwaO3dU=FdQvjKGGAJOMxGJtG6TEtdSbA@mail.gmail.com>
Date: Wed, 24 Jun 2015 15:48:06 +0530
Message-ID: 
 <CAOeZVidtdNk_6JKJ-DYykZV1ddmMyfT_ALh1mt=cuMtWwPFwYQ@mail.gmail.com>
Subject: Re: Efficient In-situ Processing of Various Storage Types on Apache
 Tajo
From: Atri Sharma <atri.jiit@gmail.com>
To: dev@tajo.apache.org
Content-Type: multipart/alternative; boundary=001a1138e85aacdba2051940d23c

--001a1138e85aacdba2051940d23c
Content-Type: text/plain; charset=UTF-8

In my opinion, operation pushdown will have to be done carefully given that
we need to be storage aware and make sure that underlying storage supports
operations.

Does this also involve join pushdowns?

On Wed, Jun 24, 2015 at 3:31 PM, Hyunsik Choi <hyunsik@apache.org> wrote:

> Hi,
>
> I had a talk at Hadoop Summit North America 2015 in Jun 17. This
> presentation is for TAJO-337 and its sub tasks. Here is my
> presentation materials. I hope that it would be helpful for you to
> understand TAJO-337 and our roadmap.
>
>
> http://www.slideshare.net/hyunsikchoi/efficient-in-situ-processing-of-various-storage-types-on-apache-tajo
>
> Best regards,
> Hyunsik
>


-- 
Regards,

Atri
*l'apprenant*

--001a1138e85aacdba2051940d23c--