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 share.code@aol.com designates
 64.12.143.82 as permitted sender)
Content-Type: text/plain; charset=euc-kr
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: [DISCUSS] 0.8.0 release and next roadmap
From: Alvin Henrick <share.code@aol.com>
In-Reply-To: <B07D2C7A-6C70-442C-A407-172239C704B4@gmail.com>
Date: Fri, 4 Apr 2014 11:06:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9A19A19-7442-4ADF-B3E0-D9D92C6ECCA7@aol.com>
References: 
 <CAM=XDd-ic-A1uV4eDy-svyhsHPM9=FEfX1FhJsB7jRGakKCQXA@mail.gmail.com>
 <B07D2C7A-6C70-442C-A407-172239C704B4@gmail.com>
To: dev@tajo.apache.org

Hi  Hyunsik ,
                      I forgot to mention in future road map we should =
also add support for PostGIS for geospatial queries (joining geometry) =
on top of Hadoop Cluster via Tajo.People need this badly and it will =
also make Tajo a unique product from it's competitors.

Thanks!
Warm Regards,
Alvin.

      =20
On Apr 4, 2014, at 10:45 AM, ktpark wrote:

> Hi Hyunsik,
>=20
> I totally agree with you that next stage should focus on working with =
thousands of large cluster nodes and many concurrent users.
> With many nodes, there must be abundant resources.
> So, how about considering implementation of push =
transmission(TAJO-291)?
>=20
> And I think Tajo needs to support different types of storage like SSD.
> Some possible usage of SSD can be cache or storage for intermediate =
data.
>=20
> I=A1=AFm very interested in JIT Query Compilation and Vectorized =
Engine(TAJO-104),
> and As I know, they are under development for Tajo in C++.
> Do we have any road map to merge those?
>=20
> 2014. 4. 4., =BF=C0=C8=C4 2:24, Hyunsik Choi <hyunsik@apache.org> =
=C0=DB=BC=BA:
>=20
>> Hi folks,
>>=20
>> I'm very happy to see that our community is growing! Also, It's a =
pleasure
>> to discuss the Tajo 0.8.0 release. Recently, I've tested various =
features
>> in various contexts, and tried to figure out if there are any =
critical
>> problems. I think that there are only a few issues and we can release =
0.8.0
>> next week. If there are further issues to be solved before the 0.8.0
>> release, feel free to suggest ideas.
>>=20
>> Also, I'd like to discuss our next roadmap. We are open to any =
suggestion
>> from users, contributors, and committers. Please fire away!
>>=20
>> I'm thinking that our next stage should focus on improving the way =
Tajo
>> runs in thousands of large cluster nodes and for a number of =
concurrent
>> users. The key issues associated with this include the following:
>>=20
>> * High availability
>> * Multi-tenancy scheduling
>> * More stability
>> * Improved shuffle
>>=20
>> The current work status is as follows. Min is working on Tajo's new
>> scheduler (TAJO-540) based on sparrow. I'll support him. As far as I =
know,
>> Alvin is working on TajoMaster HA (TAJO-704). Also, some guys =
including
>> myself are investigating and solving the issues which occur in large
>> clusters. These issues should be solved in order to make Tajo a =
complete
>> enterprise-ready production.
>>=20
>> In addition, there are some SQL feature support issues. Many analytic
>> problems require window functions. Also, in-subquery and scalar =
subquery
>> should be supported. So, I'd like to schedule them with high =
priority. In
>> my view, there will be very few SQL support issues if Tajo provides =
these
>> features.
>>=20
>> Besides those areas, David is working on a nested schema and its =
related
>> work (TAJO-710). I guess this will take quite a while because it =
requires a
>> lot of hard work. So, it would be great to schedule the nested schema
>> loosely. That's just my thoughts, anyhow.
>>=20
>> Aside from the discussion of our roadmap, I'd like to suggest that we =
need
>> to release more frequently after the 0.8.0 release. So far, there has =
been
>> a long period between each release because Tajo is undergoing heavy
>> development. By 'releasing early, releasing often', we will make more
>> tighter feedback loop between users and developers.
>>=20
>> I think that there are many additional many interesting issues to be
>> included in our roadmap. Feel free to suggest your idea. We will =
arrange
>> our short-term roadmap and long-term roadmap based on your =
suggestions.
>>=20
>> Thank you all so much for your contribution!
>>=20
>> Warm Regards,
>> Hyunsik
>=20