You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by Hyunsik Choi <hy...@apache.org> on 2015/03/16 12:13:57 UTC
[DISCUSSION] Beyond 0.10.0 release
Hi folks,
In order to share milestones with you guys and concentrate our effort
on the next release, we need to discuss the next roadmap.
Particularly, I'd like to share our direction with new contributors
due to the growing number of contributors.
As far as I know, the following major issues seem to be resolved in time.
* Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
* in subquery (https://issues.apache.org/jira/browse/TAJO-680)
* Resource allocation should be fine grained (TAJO-1397)
* ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
* Python UDF (TAJO-1344)
The above issues probably can be included in 0.11 release. If there
are missed issues, please let me know them.
Besides, the following feature issues may be on our roadmap:
* Multi-tenancy query scheduler (TAJO-540)
* More SQL features (scalar subquery, ...)
* Decimal type support
* Scalar subquery
* OLAP features (rollup, drill down, cube, ..)
* More rewrite rules (lots of issues like Unnesting of Nested Subqueries, ...)
* Make storage handler more pluggable
* Better failure handling of tasks and nodes (TAJO-1214)
* CREATE FUNCTION statement support
* CREATE TYPE statement support
* ....
Most of them are not assigned as far as I know. In addition, there are
many performance issues. I'll describe them later.
Anyway, I would be pleasure if we task about what issues you are
considering for 0.11 release or after that. I'm looking forward to
hearing you guys' feedback.
Best regards,
Hyunsik
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
Hi Dongjun,
Thank you for sharing the contents.
But, we didn't discuss any dates of future releases. We just hope that
we 0.11.0 release mid of this year. Besides, we have only 0.11 roadmap
and don't have the detailed plans of future releases. How can we
determine the release dates without roadmap?
In general, there may be two release approaches: date-based release or
feature-based release. Many open source projects including Tajo
usually follow feature-based release. In open source projects,
date-based release is very risky and is not realistic.
Open source projects are basically powered by volunteer works. Even if
many salaried contributors are participating in this project, they are
not controlled by Tajo community. In most cases, they firstly work for
what they need or they are interested in. So, we cannot force them to
firstly do specified issues in roadmap. Therefore, it is not easy to
achieve specific issues on the roadmap on specified date.
I think that the roadmap can be just a direction and some kinds of
recommendation for contributors.
Best regards,
Hyunsik
On Thu, Mar 19, 2015 at 3:27 PM, Dongjoon Hyun <do...@apache.org> wrote:
> As a user of Tajo, I want to share what I understand yesterday's meetup in
> this mailing list.
> It will be a start of further discussion. Please correct me. :)
>
> RELEASE
> ========
> 1. Tajo Community is planned QUATALY release in 2015, hopefully.
> 0.10.0 (March)
> 0.11.0 (June)
> 0.12.0 (September)
> 0.13.0 (December)
>
> 2. Minor Revision is planned MONTHLY release, hopefully.
> 0.10.1 (April)
> 0.10.2 (May)
> 0.10.3 (June)
> ...
>
> 3. Despite of lack of resource, Minor Revision is able to include 'NEW
> FEATURE without Compatibility Issues' and bug fixes.
>
> 4. For Tajo 1.0.0, we must achieve the following things.
> - Multi-tenency
> - Security
> - TPC-DS
>
>
> FEATURE
> ========
> 1. Tajo will support YARN by using APACHE SLIDER (
> http://slider.incubator.apache.org/) before June.
>
> 2. Tajo will support Pluggable Security Interface to reduce the dependancy.
> 1.1 Basic ID/Password Authentication (using RDBMS table)
> 1.2 Apache Sentry
> 1.3 Active Directory (Someday)
> 1.4 Kerberos (Someday)
>
>
> Feel free to comment anything!
>
> Thank you in advance.
>
> Warmly,
> Dongjoon.
>
>
> On Fri, Mar 20, 2015 at 6:48 AM, Hyunsik Choi <hy...@apache.org> wrote:
>>
>> If there are no further discussion, I'll update the Roadmap page in wiki.
>>
>> - hyunsik
>>
>> On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
>> > Absolutely!
>> >
>> > On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org>
> wrote:
>> >
>> >> It sounds good to me.
>> >>
>> >> Also remember 'if it doesn't happen on the mailing list, it doesn't
>> >> happen at Apache'. Please read the below mailing list thread, saying
>> >> what we must keep.
>> >>
>> >>
>> >>
> http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
>> >>
>> >> Best regards,
>> >> Hyunsik
>> >>
>> >> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org>
>> >> wrote:
>> >> > Today we have a Tajo regional meetup in Seoul. What about discussing
> this
>> >> > issue in detail there?
>> >> >
>> >> > Of course, we should post the result here, too.
>> >> >
>> >> > Warmly,
>> >> > Dongjoon
>> >> >
>> >> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
>> >> >
>> >> >> The major issues looks good to me for 0.11.0 release
>> >> >> Thank you.
>> >> >>
>> >> >> -Jinho
>> >> >> Best regards
>> >> >>
>> >> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
>> >> <javascript:;>
>> >> >> >:
>> >> >>
>> >> >> > Hi folks,
>> >> >> >
>> >> >> > In order to share milestones with you guys and concentrate our
> effort
>> >> >> > on the next release, we need to discuss the next roadmap.
>> >> >> > Particularly, I'd like to share our direction with new
> contributors
>> >> >> > due to the growing number of contributors.
>> >> >> >
>> >> >> > As far as I know, the following major issues seem to be resolved
> in
>> >> time.
>> >> >> >
>> >> >> > * Nested complex type (
> https://issues.apache.org/jira/browse/TAJO-721
>> >> )
>> >> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>> >> >> > * Resource allocation should be fine grained (TAJO-1397)
>> >> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>> >> >> > * Python UDF (TAJO-1344)
>> >> >> >
>> >> >> > The above issues probably can be included in 0.11 release. If
> there
>> >> >> > are missed issues, please let me know them.
>> >> >> >
>> >> >> >
>> >> >> > Besides, the following feature issues may be on our roadmap:
>> >> >> >
>> >> >> > * Multi-tenancy query scheduler (TAJO-540)
>> >> >> > * More SQL features (scalar subquery, ...)
>> >> >> > * Decimal type support
>> >> >> > * Scalar subquery
>> >> >> > * OLAP features (rollup, drill down, cube, ..)
>> >> >> > * More rewrite rules (lots of issues like Unnesting of Nested
>> >> Subqueries,
>> >> >> > ...)
>> >> >> > * Make storage handler more pluggable
>> >> >> > * Better failure handling of tasks and nodes (TAJO-1214)
>> >> >> > * CREATE FUNCTION statement support
>> >> >> > * CREATE TYPE statement support
>> >> >> > * ....
>> >> >> >
>> >> >> > Most of them are not assigned as far as I know. In addition,
> there are
>> >> >> > many performance issues. I'll describe them later.
>> >> >> >
>> >> >> > Anyway, I would be pleasure if we task about what issues you are
>> >> >> > considering for 0.11 release or after that. I'm looking forward to
>> >> >> > hearing you guys' feedback.
>> >> >> >
>> >> >> >
>> >> >> > Best regards,
>> >> >> > Hyunsik
>> >> >> >
>> >> >>
>> >>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@apache.org>.
As a user of Tajo, I want to share what I understand yesterday's meetup in
this mailing list.
It will be a start of further discussion. Please correct me. :)
RELEASE
========
1. Tajo Community is planned QUATALY release in 2015, hopefully.
0.10.0 (March)
0.11.0 (June)
0.12.0 (September)
0.13.0 (December)
2. Minor Revision is planned MONTHLY release, hopefully.
0.10.1 (April)
0.10.2 (May)
0.10.3 (June)
...
3. Despite of lack of resource, Minor Revision is able to include 'NEW
FEATURE without Compatibility Issues' and bug fixes.
4. For Tajo 1.0.0, we must achieve the following things.
- Multi-tenency
- Security
- TPC-DS
FEATURE
========
1. Tajo will support YARN by using APACHE SLIDER (
http://slider.incubator.apache.org/) before June.
2. Tajo will support Pluggable Security Interface to reduce the dependancy.
1.1 Basic ID/Password Authentication (using RDBMS table)
1.2 Apache Sentry
1.3 Active Directory (Someday)
1.4 Kerberos (Someday)
Feel free to comment anything!
Thank you in advance.
Warmly,
Dongjoon.
On Fri, Mar 20, 2015 at 6:48 AM, Hyunsik Choi <hy...@apache.org> wrote:
>
> If there are no further discussion, I'll update the Roadmap page in wiki.
>
> - hyunsik
>
> On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <do...@apache.org>
wrote:
> > Absolutely!
> >
> > On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org>
wrote:
> >
> >> It sounds good to me.
> >>
> >> Also remember 'if it doesn't happen on the mailing list, it doesn't
> >> happen at Apache'. Please read the below mailing list thread, saying
> >> what we must keep.
> >>
> >>
> >>
http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
> >>
> >> Best regards,
> >> Hyunsik
> >>
> >> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org>
> >> wrote:
> >> > Today we have a Tajo regional meetup in Seoul. What about discussing
this
> >> > issue in detail there?
> >> >
> >> > Of course, we should post the result here, too.
> >> >
> >> > Warmly,
> >> > Dongjoon
> >> >
> >> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
> >> >
> >> >> The major issues looks good to me for 0.11.0 release
> >> >> Thank you.
> >> >>
> >> >> -Jinho
> >> >> Best regards
> >> >>
> >> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
> >> <javascript:;>
> >> >> >:
> >> >>
> >> >> > Hi folks,
> >> >> >
> >> >> > In order to share milestones with you guys and concentrate our
effort
> >> >> > on the next release, we need to discuss the next roadmap.
> >> >> > Particularly, I'd like to share our direction with new
contributors
> >> >> > due to the growing number of contributors.
> >> >> >
> >> >> > As far as I know, the following major issues seem to be resolved
in
> >> time.
> >> >> >
> >> >> > * Nested complex type (
https://issues.apache.org/jira/browse/TAJO-721
> >> )
> >> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> >> >> > * Resource allocation should be fine grained (TAJO-1397)
> >> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> >> >> > * Python UDF (TAJO-1344)
> >> >> >
> >> >> > The above issues probably can be included in 0.11 release. If
there
> >> >> > are missed issues, please let me know them.
> >> >> >
> >> >> >
> >> >> > Besides, the following feature issues may be on our roadmap:
> >> >> >
> >> >> > * Multi-tenancy query scheduler (TAJO-540)
> >> >> > * More SQL features (scalar subquery, ...)
> >> >> > * Decimal type support
> >> >> > * Scalar subquery
> >> >> > * OLAP features (rollup, drill down, cube, ..)
> >> >> > * More rewrite rules (lots of issues like Unnesting of Nested
> >> Subqueries,
> >> >> > ...)
> >> >> > * Make storage handler more pluggable
> >> >> > * Better failure handling of tasks and nodes (TAJO-1214)
> >> >> > * CREATE FUNCTION statement support
> >> >> > * CREATE TYPE statement support
> >> >> > * ....
> >> >> >
> >> >> > Most of them are not assigned as far as I know. In addition,
there are
> >> >> > many performance issues. I'll describe them later.
> >> >> >
> >> >> > Anyway, I would be pleasure if we task about what issues you are
> >> >> > considering for 0.11 release or after that. I'm looking forward to
> >> >> > hearing you guys' feedback.
> >> >> >
> >> >> >
> >> >> > Best regards,
> >> >> > Hyunsik
> >> >> >
> >> >>
> >>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@apache.org>.
Hmm. I agree with Hyunsik and Jihoon and no objections for that.
Hyunsik and you didn't say anydate like that. That's true. :-)
Warmly,
Dongjoon.
On Fri, Mar 20, 2015 at 11:59 AM, Jihoon Son <ji...@apache.org> wrote:
> I was the host of the community meetup yesterday.
>
> We had some discussions on the recent 0.10.0 release.
> In addition, we also had some discussions on our changed release policy
> which is already discussed in our mailing list. Finally, I introduced our
> future roadmap that is also being discussed in this thread.
>
> However, we have NEVER discussed any fixed release schedules. Honestly, we
> don't have any fixed release schedules. I know we have released every 5
> months before, but it was just a coincidence. So, I just said that the tajo
> community is trying to release more faster. The schedules that Dongjoon
> shared in this thread were just the hopes of some PMCs and Committers. It
> does not delegate the Tajo community.
>
> As Hyunsik aforementioned, our release schedule is decided based on
> features. When ALL PMC members agree, it's the time to release.
>
> Sincerely,
> Jihoon
>
> On Fri, Mar 20, 2015 at 11:33 AM Dongjoon Hyun <do...@apache.org>
> wrote:
>
> > I see. No problem at all for me! Then, I think the final decision is made
> > in Tajo Community.
> > The best and only way is to speed up Tajo Community Activity more.
> > Thank you, Hyunsik!
> >
> > Best regards,
> > Dongjoon.
> >
> > On Fri, Mar 20, 2015 at 8:05 AM, Hyunsik Choi <hy...@apache.org>
> wrote:
> >
> > > Minor release will be usually depend on our bug fixes. If we find some
> > > critical bug, we should release the bug fix release immediately.
> > > Otherwise, it can be release them monthly by merging recent bug fixes
> > > after some release.
> > >
> > > Best regards,
> > > Hyunsik
> > >
> > > On Thu, Mar 19, 2015 at 3:52 PM, Dongjoon Hyun <do...@apache.org>
> > > wrote:
> > > > Thank you, @hyunsik. I'm happy since the roadmap page has all of the
> > > > details, now.
> > > > By the way, could you mention that Regular Minor Release Plan in any
> > way?
> > > > Or, do you want to omit the Minor Releases like 2014?
> > > > Both are fine to me.
> > > > I just want to work according to Official Tajo Roadmap.
> > > >
> > > > Best regards,
> > > > Dongjoon.
> > > >
> > > >
> > > > On Fri, Mar 20, 2015 at 7:35 AM, Hyunsik Choi <hy...@apache.org>
> > > wrote:
> > > >
> > > >> Hi guys,
> > > >>
> > > >> I roughly updated the roadmap for 0.11.0. Also, I also arranged the
> > > >> roadmap 1.0.0.
> > > >> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap
> > > >>
> > > >> I welcome any feedback.
> > > >>
> > > >> Best regards,
> > > >> Hyunsik
> > > >>
> > > >> On Thu, Mar 19, 2015 at 2:48 PM, Hyunsik Choi <hy...@apache.org>
> > > wrote:
> > > >> > If there are no further discussion, I'll update the Roadmap page
> in
> > > wiki.
> > > >> >
> > > >> > - hyunsik
> > > >> >
> > > >> > On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <
> dongjoon@apache.org
> > >
> > > >> wrote:
> > > >> >> Absolutely!
> > > >> >>
> > > >> >> On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <
> hyunsik@apache.org>
> > > >> wrote:
> > > >> >>
> > > >> >>> It sounds good to me.
> > > >> >>>
> > > >> >>> Also remember 'if it doesn't happen on the mailing list, it
> > doesn't
> > > >> >>> happen at Apache'. Please read the below mailing list thread,
> > saying
> > > >> >>> what we must keep.
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >>
> > > http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%
> > 3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
> > > >> >>>
> > > >> >>> Best regards,
> > > >> >>> Hyunsik
> > > >> >>>
> > > >> >>> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <
> > dongjoon@apache.org
> > > >
> > > >> >>> wrote:
> > > >> >>> > Today we have a Tajo regional meetup in Seoul. What about
> > > discussing
> > > >> this
> > > >> >>> > issue in detail there?
> > > >> >>> >
> > > >> >>> > Of course, we should post the result here, too.
> > > >> >>> >
> > > >> >>> > Warmly,
> > > >> >>> > Dongjoon
> > > >> >>> >
> > > >> >>> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org>
> wrote:
> > > >> >>> >
> > > >> >>> >> The major issues looks good to me for 0.11.0 release
> > > >> >>> >> Thank you.
> > > >> >>> >>
> > > >> >>> >> -Jinho
> > > >> >>> >> Best regards
> > > >> >>> >>
> > > >> >>> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
> > > >> >>> <javascript:;>
> > > >> >>> >> >:
> > > >> >>> >>
> > > >> >>> >> > Hi folks,
> > > >> >>> >> >
> > > >> >>> >> > In order to share milestones with you guys and concentrate
> > our
> > > >> effort
> > > >> >>> >> > on the next release, we need to discuss the next roadmap.
> > > >> >>> >> > Particularly, I'd like to share our direction with new
> > > >> contributors
> > > >> >>> >> > due to the growing number of contributors.
> > > >> >>> >> >
> > > >> >>> >> > As far as I know, the following major issues seem to be
> > > resolved
> > > >> in
> > > >> >>> time.
> > > >> >>> >> >
> > > >> >>> >> > * Nested complex type (
> > > >> https://issues.apache.org/jira/browse/TAJO-721
> > > >> >>> )
> > > >> >>> >> > * in subquery (https://issues.apache.org/
> > jira/browse/TAJO-680)
> > > >> >>> >> > * Resource allocation should be fine grained (TAJO-1397)
> > > >> >>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> > > >> >>> >> > * Python UDF (TAJO-1344)
> > > >> >>> >> >
> > > >> >>> >> > The above issues probably can be included in 0.11 release.
> If
> > > >> there
> > > >> >>> >> > are missed issues, please let me know them.
> > > >> >>> >> >
> > > >> >>> >> >
> > > >> >>> >> > Besides, the following feature issues may be on our
> roadmap:
> > > >> >>> >> >
> > > >> >>> >> > * Multi-tenancy query scheduler (TAJO-540)
> > > >> >>> >> > * More SQL features (scalar subquery, ...)
> > > >> >>> >> > * Decimal type support
> > > >> >>> >> > * Scalar subquery
> > > >> >>> >> > * OLAP features (rollup, drill down, cube, ..)
> > > >> >>> >> > * More rewrite rules (lots of issues like Unnesting of
> Nested
> > > >> >>> Subqueries,
> > > >> >>> >> > ...)
> > > >> >>> >> > * Make storage handler more pluggable
> > > >> >>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
> > > >> >>> >> > * CREATE FUNCTION statement support
> > > >> >>> >> > * CREATE TYPE statement support
> > > >> >>> >> > * ....
> > > >> >>> >> >
> > > >> >>> >> > Most of them are not assigned as far as I know. In
> addition,
> > > >> there are
> > > >> >>> >> > many performance issues. I'll describe them later.
> > > >> >>> >> >
> > > >> >>> >> > Anyway, I would be pleasure if we task about what issues
> you
> > > are
> > > >> >>> >> > considering for 0.11 release or after that. I'm looking
> > > forward to
> > > >> >>> >> > hearing you guys' feedback.
> > > >> >>> >> >
> > > >> >>> >> >
> > > >> >>> >> > Best regards,
> > > >> >>> >> > Hyunsik
> > > >> >>> >> >
> > > >> >>> >>
> > > >> >>>
> > > >>
> > >
> >
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Jihoon Son <ji...@apache.org>.
I was the host of the community meetup yesterday.
We had some discussions on the recent 0.10.0 release.
In addition, we also had some discussions on our changed release policy
which is already discussed in our mailing list. Finally, I introduced our
future roadmap that is also being discussed in this thread.
However, we have NEVER discussed any fixed release schedules. Honestly, we
don't have any fixed release schedules. I know we have released every 5
months before, but it was just a coincidence. So, I just said that the tajo
community is trying to release more faster. The schedules that Dongjoon
shared in this thread were just the hopes of some PMCs and Committers. It
does not delegate the Tajo community.
As Hyunsik aforementioned, our release schedule is decided based on
features. When ALL PMC members agree, it's the time to release.
Sincerely,
Jihoon
On Fri, Mar 20, 2015 at 11:33 AM Dongjoon Hyun <do...@apache.org> wrote:
> I see. No problem at all for me! Then, I think the final decision is made
> in Tajo Community.
> The best and only way is to speed up Tajo Community Activity more.
> Thank you, Hyunsik!
>
> Best regards,
> Dongjoon.
>
> On Fri, Mar 20, 2015 at 8:05 AM, Hyunsik Choi <hy...@apache.org> wrote:
>
> > Minor release will be usually depend on our bug fixes. If we find some
> > critical bug, we should release the bug fix release immediately.
> > Otherwise, it can be release them monthly by merging recent bug fixes
> > after some release.
> >
> > Best regards,
> > Hyunsik
> >
> > On Thu, Mar 19, 2015 at 3:52 PM, Dongjoon Hyun <do...@apache.org>
> > wrote:
> > > Thank you, @hyunsik. I'm happy since the roadmap page has all of the
> > > details, now.
> > > By the way, could you mention that Regular Minor Release Plan in any
> way?
> > > Or, do you want to omit the Minor Releases like 2014?
> > > Both are fine to me.
> > > I just want to work according to Official Tajo Roadmap.
> > >
> > > Best regards,
> > > Dongjoon.
> > >
> > >
> > > On Fri, Mar 20, 2015 at 7:35 AM, Hyunsik Choi <hy...@apache.org>
> > wrote:
> > >
> > >> Hi guys,
> > >>
> > >> I roughly updated the roadmap for 0.11.0. Also, I also arranged the
> > >> roadmap 1.0.0.
> > >> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap
> > >>
> > >> I welcome any feedback.
> > >>
> > >> Best regards,
> > >> Hyunsik
> > >>
> > >> On Thu, Mar 19, 2015 at 2:48 PM, Hyunsik Choi <hy...@apache.org>
> > wrote:
> > >> > If there are no further discussion, I'll update the Roadmap page in
> > wiki.
> > >> >
> > >> > - hyunsik
> > >> >
> > >> > On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <dongjoon@apache.org
> >
> > >> wrote:
> > >> >> Absolutely!
> > >> >>
> > >> >> On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org>
> > >> wrote:
> > >> >>
> > >> >>> It sounds good to me.
> > >> >>>
> > >> >>> Also remember 'if it doesn't happen on the mailing list, it
> doesn't
> > >> >>> happen at Apache'. Please read the below mailing list thread,
> saying
> > >> >>> what we must keep.
> > >> >>>
> > >> >>>
> > >> >>>
> > >>
> > http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%
> 3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
> > >> >>>
> > >> >>> Best regards,
> > >> >>> Hyunsik
> > >> >>>
> > >> >>> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <
> dongjoon@apache.org
> > >
> > >> >>> wrote:
> > >> >>> > Today we have a Tajo regional meetup in Seoul. What about
> > discussing
> > >> this
> > >> >>> > issue in detail there?
> > >> >>> >
> > >> >>> > Of course, we should post the result here, too.
> > >> >>> >
> > >> >>> > Warmly,
> > >> >>> > Dongjoon
> > >> >>> >
> > >> >>> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
> > >> >>> >
> > >> >>> >> The major issues looks good to me for 0.11.0 release
> > >> >>> >> Thank you.
> > >> >>> >>
> > >> >>> >> -Jinho
> > >> >>> >> Best regards
> > >> >>> >>
> > >> >>> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
> > >> >>> <javascript:;>
> > >> >>> >> >:
> > >> >>> >>
> > >> >>> >> > Hi folks,
> > >> >>> >> >
> > >> >>> >> > In order to share milestones with you guys and concentrate
> our
> > >> effort
> > >> >>> >> > on the next release, we need to discuss the next roadmap.
> > >> >>> >> > Particularly, I'd like to share our direction with new
> > >> contributors
> > >> >>> >> > due to the growing number of contributors.
> > >> >>> >> >
> > >> >>> >> > As far as I know, the following major issues seem to be
> > resolved
> > >> in
> > >> >>> time.
> > >> >>> >> >
> > >> >>> >> > * Nested complex type (
> > >> https://issues.apache.org/jira/browse/TAJO-721
> > >> >>> )
> > >> >>> >> > * in subquery (https://issues.apache.org/
> jira/browse/TAJO-680)
> > >> >>> >> > * Resource allocation should be fine grained (TAJO-1397)
> > >> >>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> > >> >>> >> > * Python UDF (TAJO-1344)
> > >> >>> >> >
> > >> >>> >> > The above issues probably can be included in 0.11 release. If
> > >> there
> > >> >>> >> > are missed issues, please let me know them.
> > >> >>> >> >
> > >> >>> >> >
> > >> >>> >> > Besides, the following feature issues may be on our roadmap:
> > >> >>> >> >
> > >> >>> >> > * Multi-tenancy query scheduler (TAJO-540)
> > >> >>> >> > * More SQL features (scalar subquery, ...)
> > >> >>> >> > * Decimal type support
> > >> >>> >> > * Scalar subquery
> > >> >>> >> > * OLAP features (rollup, drill down, cube, ..)
> > >> >>> >> > * More rewrite rules (lots of issues like Unnesting of Nested
> > >> >>> Subqueries,
> > >> >>> >> > ...)
> > >> >>> >> > * Make storage handler more pluggable
> > >> >>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
> > >> >>> >> > * CREATE FUNCTION statement support
> > >> >>> >> > * CREATE TYPE statement support
> > >> >>> >> > * ....
> > >> >>> >> >
> > >> >>> >> > Most of them are not assigned as far as I know. In addition,
> > >> there are
> > >> >>> >> > many performance issues. I'll describe them later.
> > >> >>> >> >
> > >> >>> >> > Anyway, I would be pleasure if we task about what issues you
> > are
> > >> >>> >> > considering for 0.11 release or after that. I'm looking
> > forward to
> > >> >>> >> > hearing you guys' feedback.
> > >> >>> >> >
> > >> >>> >> >
> > >> >>> >> > Best regards,
> > >> >>> >> > Hyunsik
> > >> >>> >> >
> > >> >>> >>
> > >> >>>
> > >>
> >
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@apache.org>.
I see. No problem at all for me! Then, I think the final decision is made
in Tajo Community.
The best and only way is to speed up Tajo Community Activity more.
Thank you, Hyunsik!
Best regards,
Dongjoon.
On Fri, Mar 20, 2015 at 8:05 AM, Hyunsik Choi <hy...@apache.org> wrote:
> Minor release will be usually depend on our bug fixes. If we find some
> critical bug, we should release the bug fix release immediately.
> Otherwise, it can be release them monthly by merging recent bug fixes
> after some release.
>
> Best regards,
> Hyunsik
>
> On Thu, Mar 19, 2015 at 3:52 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
> > Thank you, @hyunsik. I'm happy since the roadmap page has all of the
> > details, now.
> > By the way, could you mention that Regular Minor Release Plan in any way?
> > Or, do you want to omit the Minor Releases like 2014?
> > Both are fine to me.
> > I just want to work according to Official Tajo Roadmap.
> >
> > Best regards,
> > Dongjoon.
> >
> >
> > On Fri, Mar 20, 2015 at 7:35 AM, Hyunsik Choi <hy...@apache.org>
> wrote:
> >
> >> Hi guys,
> >>
> >> I roughly updated the roadmap for 0.11.0. Also, I also arranged the
> >> roadmap 1.0.0.
> >> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap
> >>
> >> I welcome any feedback.
> >>
> >> Best regards,
> >> Hyunsik
> >>
> >> On Thu, Mar 19, 2015 at 2:48 PM, Hyunsik Choi <hy...@apache.org>
> wrote:
> >> > If there are no further discussion, I'll update the Roadmap page in
> wiki.
> >> >
> >> > - hyunsik
> >> >
> >> > On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <do...@apache.org>
> >> wrote:
> >> >> Absolutely!
> >> >>
> >> >> On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org>
> >> wrote:
> >> >>
> >> >>> It sounds good to me.
> >> >>>
> >> >>> Also remember 'if it doesn't happen on the mailing list, it doesn't
> >> >>> happen at Apache'. Please read the below mailing list thread, saying
> >> >>> what we must keep.
> >> >>>
> >> >>>
> >> >>>
> >>
> http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
> >> >>>
> >> >>> Best regards,
> >> >>> Hyunsik
> >> >>>
> >> >>> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <dongjoon@apache.org
> >
> >> >>> wrote:
> >> >>> > Today we have a Tajo regional meetup in Seoul. What about
> discussing
> >> this
> >> >>> > issue in detail there?
> >> >>> >
> >> >>> > Of course, we should post the result here, too.
> >> >>> >
> >> >>> > Warmly,
> >> >>> > Dongjoon
> >> >>> >
> >> >>> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
> >> >>> >
> >> >>> >> The major issues looks good to me for 0.11.0 release
> >> >>> >> Thank you.
> >> >>> >>
> >> >>> >> -Jinho
> >> >>> >> Best regards
> >> >>> >>
> >> >>> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
> >> >>> <javascript:;>
> >> >>> >> >:
> >> >>> >>
> >> >>> >> > Hi folks,
> >> >>> >> >
> >> >>> >> > In order to share milestones with you guys and concentrate our
> >> effort
> >> >>> >> > on the next release, we need to discuss the next roadmap.
> >> >>> >> > Particularly, I'd like to share our direction with new
> >> contributors
> >> >>> >> > due to the growing number of contributors.
> >> >>> >> >
> >> >>> >> > As far as I know, the following major issues seem to be
> resolved
> >> in
> >> >>> time.
> >> >>> >> >
> >> >>> >> > * Nested complex type (
> >> https://issues.apache.org/jira/browse/TAJO-721
> >> >>> )
> >> >>> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> >> >>> >> > * Resource allocation should be fine grained (TAJO-1397)
> >> >>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> >> >>> >> > * Python UDF (TAJO-1344)
> >> >>> >> >
> >> >>> >> > The above issues probably can be included in 0.11 release. If
> >> there
> >> >>> >> > are missed issues, please let me know them.
> >> >>> >> >
> >> >>> >> >
> >> >>> >> > Besides, the following feature issues may be on our roadmap:
> >> >>> >> >
> >> >>> >> > * Multi-tenancy query scheduler (TAJO-540)
> >> >>> >> > * More SQL features (scalar subquery, ...)
> >> >>> >> > * Decimal type support
> >> >>> >> > * Scalar subquery
> >> >>> >> > * OLAP features (rollup, drill down, cube, ..)
> >> >>> >> > * More rewrite rules (lots of issues like Unnesting of Nested
> >> >>> Subqueries,
> >> >>> >> > ...)
> >> >>> >> > * Make storage handler more pluggable
> >> >>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
> >> >>> >> > * CREATE FUNCTION statement support
> >> >>> >> > * CREATE TYPE statement support
> >> >>> >> > * ....
> >> >>> >> >
> >> >>> >> > Most of them are not assigned as far as I know. In addition,
> >> there are
> >> >>> >> > many performance issues. I'll describe them later.
> >> >>> >> >
> >> >>> >> > Anyway, I would be pleasure if we task about what issues you
> are
> >> >>> >> > considering for 0.11 release or after that. I'm looking
> forward to
> >> >>> >> > hearing you guys' feedback.
> >> >>> >> >
> >> >>> >> >
> >> >>> >> > Best regards,
> >> >>> >> > Hyunsik
> >> >>> >> >
> >> >>> >>
> >> >>>
> >>
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
Minor release will be usually depend on our bug fixes. If we find some
critical bug, we should release the bug fix release immediately.
Otherwise, it can be release them monthly by merging recent bug fixes
after some release.
Best regards,
Hyunsik
On Thu, Mar 19, 2015 at 3:52 PM, Dongjoon Hyun <do...@apache.org> wrote:
> Thank you, @hyunsik. I'm happy since the roadmap page has all of the
> details, now.
> By the way, could you mention that Regular Minor Release Plan in any way?
> Or, do you want to omit the Minor Releases like 2014?
> Both are fine to me.
> I just want to work according to Official Tajo Roadmap.
>
> Best regards,
> Dongjoon.
>
>
> On Fri, Mar 20, 2015 at 7:35 AM, Hyunsik Choi <hy...@apache.org> wrote:
>
>> Hi guys,
>>
>> I roughly updated the roadmap for 0.11.0. Also, I also arranged the
>> roadmap 1.0.0.
>> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap
>>
>> I welcome any feedback.
>>
>> Best regards,
>> Hyunsik
>>
>> On Thu, Mar 19, 2015 at 2:48 PM, Hyunsik Choi <hy...@apache.org> wrote:
>> > If there are no further discussion, I'll update the Roadmap page in wiki.
>> >
>> > - hyunsik
>> >
>> > On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <do...@apache.org>
>> wrote:
>> >> Absolutely!
>> >>
>> >> On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org>
>> wrote:
>> >>
>> >>> It sounds good to me.
>> >>>
>> >>> Also remember 'if it doesn't happen on the mailing list, it doesn't
>> >>> happen at Apache'. Please read the below mailing list thread, saying
>> >>> what we must keep.
>> >>>
>> >>>
>> >>>
>> http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
>> >>>
>> >>> Best regards,
>> >>> Hyunsik
>> >>>
>> >>> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org>
>> >>> wrote:
>> >>> > Today we have a Tajo regional meetup in Seoul. What about discussing
>> this
>> >>> > issue in detail there?
>> >>> >
>> >>> > Of course, we should post the result here, too.
>> >>> >
>> >>> > Warmly,
>> >>> > Dongjoon
>> >>> >
>> >>> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
>> >>> >
>> >>> >> The major issues looks good to me for 0.11.0 release
>> >>> >> Thank you.
>> >>> >>
>> >>> >> -Jinho
>> >>> >> Best regards
>> >>> >>
>> >>> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
>> >>> <javascript:;>
>> >>> >> >:
>> >>> >>
>> >>> >> > Hi folks,
>> >>> >> >
>> >>> >> > In order to share milestones with you guys and concentrate our
>> effort
>> >>> >> > on the next release, we need to discuss the next roadmap.
>> >>> >> > Particularly, I'd like to share our direction with new
>> contributors
>> >>> >> > due to the growing number of contributors.
>> >>> >> >
>> >>> >> > As far as I know, the following major issues seem to be resolved
>> in
>> >>> time.
>> >>> >> >
>> >>> >> > * Nested complex type (
>> https://issues.apache.org/jira/browse/TAJO-721
>> >>> )
>> >>> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>> >>> >> > * Resource allocation should be fine grained (TAJO-1397)
>> >>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>> >>> >> > * Python UDF (TAJO-1344)
>> >>> >> >
>> >>> >> > The above issues probably can be included in 0.11 release. If
>> there
>> >>> >> > are missed issues, please let me know them.
>> >>> >> >
>> >>> >> >
>> >>> >> > Besides, the following feature issues may be on our roadmap:
>> >>> >> >
>> >>> >> > * Multi-tenancy query scheduler (TAJO-540)
>> >>> >> > * More SQL features (scalar subquery, ...)
>> >>> >> > * Decimal type support
>> >>> >> > * Scalar subquery
>> >>> >> > * OLAP features (rollup, drill down, cube, ..)
>> >>> >> > * More rewrite rules (lots of issues like Unnesting of Nested
>> >>> Subqueries,
>> >>> >> > ...)
>> >>> >> > * Make storage handler more pluggable
>> >>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
>> >>> >> > * CREATE FUNCTION statement support
>> >>> >> > * CREATE TYPE statement support
>> >>> >> > * ....
>> >>> >> >
>> >>> >> > Most of them are not assigned as far as I know. In addition,
>> there are
>> >>> >> > many performance issues. I'll describe them later.
>> >>> >> >
>> >>> >> > Anyway, I would be pleasure if we task about what issues you are
>> >>> >> > considering for 0.11 release or after that. I'm looking forward to
>> >>> >> > hearing you guys' feedback.
>> >>> >> >
>> >>> >> >
>> >>> >> > Best regards,
>> >>> >> > Hyunsik
>> >>> >> >
>> >>> >>
>> >>>
>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@apache.org>.
Thank you, @hyunsik. I'm happy since the roadmap page has all of the
details, now.
By the way, could you mention that Regular Minor Release Plan in any way?
Or, do you want to omit the Minor Releases like 2014?
Both are fine to me.
I just want to work according to Official Tajo Roadmap.
Best regards,
Dongjoon.
On Fri, Mar 20, 2015 at 7:35 AM, Hyunsik Choi <hy...@apache.org> wrote:
> Hi guys,
>
> I roughly updated the roadmap for 0.11.0. Also, I also arranged the
> roadmap 1.0.0.
> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap
>
> I welcome any feedback.
>
> Best regards,
> Hyunsik
>
> On Thu, Mar 19, 2015 at 2:48 PM, Hyunsik Choi <hy...@apache.org> wrote:
> > If there are no further discussion, I'll update the Roadmap page in wiki.
> >
> > - hyunsik
> >
> > On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
> >> Absolutely!
> >>
> >> On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org>
> wrote:
> >>
> >>> It sounds good to me.
> >>>
> >>> Also remember 'if it doesn't happen on the mailing list, it doesn't
> >>> happen at Apache'. Please read the below mailing list thread, saying
> >>> what we must keep.
> >>>
> >>>
> >>>
> http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
> >>>
> >>> Best regards,
> >>> Hyunsik
> >>>
> >>> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org>
> >>> wrote:
> >>> > Today we have a Tajo regional meetup in Seoul. What about discussing
> this
> >>> > issue in detail there?
> >>> >
> >>> > Of course, we should post the result here, too.
> >>> >
> >>> > Warmly,
> >>> > Dongjoon
> >>> >
> >>> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
> >>> >
> >>> >> The major issues looks good to me for 0.11.0 release
> >>> >> Thank you.
> >>> >>
> >>> >> -Jinho
> >>> >> Best regards
> >>> >>
> >>> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
> >>> <javascript:;>
> >>> >> >:
> >>> >>
> >>> >> > Hi folks,
> >>> >> >
> >>> >> > In order to share milestones with you guys and concentrate our
> effort
> >>> >> > on the next release, we need to discuss the next roadmap.
> >>> >> > Particularly, I'd like to share our direction with new
> contributors
> >>> >> > due to the growing number of contributors.
> >>> >> >
> >>> >> > As far as I know, the following major issues seem to be resolved
> in
> >>> time.
> >>> >> >
> >>> >> > * Nested complex type (
> https://issues.apache.org/jira/browse/TAJO-721
> >>> )
> >>> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> >>> >> > * Resource allocation should be fine grained (TAJO-1397)
> >>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> >>> >> > * Python UDF (TAJO-1344)
> >>> >> >
> >>> >> > The above issues probably can be included in 0.11 release. If
> there
> >>> >> > are missed issues, please let me know them.
> >>> >> >
> >>> >> >
> >>> >> > Besides, the following feature issues may be on our roadmap:
> >>> >> >
> >>> >> > * Multi-tenancy query scheduler (TAJO-540)
> >>> >> > * More SQL features (scalar subquery, ...)
> >>> >> > * Decimal type support
> >>> >> > * Scalar subquery
> >>> >> > * OLAP features (rollup, drill down, cube, ..)
> >>> >> > * More rewrite rules (lots of issues like Unnesting of Nested
> >>> Subqueries,
> >>> >> > ...)
> >>> >> > * Make storage handler more pluggable
> >>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
> >>> >> > * CREATE FUNCTION statement support
> >>> >> > * CREATE TYPE statement support
> >>> >> > * ....
> >>> >> >
> >>> >> > Most of them are not assigned as far as I know. In addition,
> there are
> >>> >> > many performance issues. I'll describe them later.
> >>> >> >
> >>> >> > Anyway, I would be pleasure if we task about what issues you are
> >>> >> > considering for 0.11 release or after that. I'm looking forward to
> >>> >> > hearing you guys' feedback.
> >>> >> >
> >>> >> >
> >>> >> > Best regards,
> >>> >> > Hyunsik
> >>> >> >
> >>> >>
> >>>
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
Hi guys,
I roughly updated the roadmap for 0.11.0. Also, I also arranged the
roadmap 1.0.0.
https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap
I welcome any feedback.
Best regards,
Hyunsik
On Thu, Mar 19, 2015 at 2:48 PM, Hyunsik Choi <hy...@apache.org> wrote:
> If there are no further discussion, I'll update the Roadmap page in wiki.
>
> - hyunsik
>
> On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <do...@apache.org> wrote:
>> Absolutely!
>>
>> On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org> wrote:
>>
>>> It sounds good to me.
>>>
>>> Also remember 'if it doesn't happen on the mailing list, it doesn't
>>> happen at Apache'. Please read the below mailing list thread, saying
>>> what we must keep.
>>>
>>>
>>> http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
>>>
>>> Best regards,
>>> Hyunsik
>>>
>>> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org>
>>> wrote:
>>> > Today we have a Tajo regional meetup in Seoul. What about discussing this
>>> > issue in detail there?
>>> >
>>> > Of course, we should post the result here, too.
>>> >
>>> > Warmly,
>>> > Dongjoon
>>> >
>>> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
>>> >
>>> >> The major issues looks good to me for 0.11.0 release
>>> >> Thank you.
>>> >>
>>> >> -Jinho
>>> >> Best regards
>>> >>
>>> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
>>> <javascript:;>
>>> >> >:
>>> >>
>>> >> > Hi folks,
>>> >> >
>>> >> > In order to share milestones with you guys and concentrate our effort
>>> >> > on the next release, we need to discuss the next roadmap.
>>> >> > Particularly, I'd like to share our direction with new contributors
>>> >> > due to the growing number of contributors.
>>> >> >
>>> >> > As far as I know, the following major issues seem to be resolved in
>>> time.
>>> >> >
>>> >> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721
>>> )
>>> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>>> >> > * Resource allocation should be fine grained (TAJO-1397)
>>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>>> >> > * Python UDF (TAJO-1344)
>>> >> >
>>> >> > The above issues probably can be included in 0.11 release. If there
>>> >> > are missed issues, please let me know them.
>>> >> >
>>> >> >
>>> >> > Besides, the following feature issues may be on our roadmap:
>>> >> >
>>> >> > * Multi-tenancy query scheduler (TAJO-540)
>>> >> > * More SQL features (scalar subquery, ...)
>>> >> > * Decimal type support
>>> >> > * Scalar subquery
>>> >> > * OLAP features (rollup, drill down, cube, ..)
>>> >> > * More rewrite rules (lots of issues like Unnesting of Nested
>>> Subqueries,
>>> >> > ...)
>>> >> > * Make storage handler more pluggable
>>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
>>> >> > * CREATE FUNCTION statement support
>>> >> > * CREATE TYPE statement support
>>> >> > * ....
>>> >> >
>>> >> > Most of them are not assigned as far as I know. In addition, there are
>>> >> > many performance issues. I'll describe them later.
>>> >> >
>>> >> > Anyway, I would be pleasure if we task about what issues you are
>>> >> > considering for 0.11 release or after that. I'm looking forward to
>>> >> > hearing you guys' feedback.
>>> >> >
>>> >> >
>>> >> > Best regards,
>>> >> > Hyunsik
>>> >> >
>>> >>
>>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
If there are no further discussion, I'll update the Roadmap page in wiki.
- hyunsik
On Wed, Mar 18, 2015 at 4:01 PM, Dongjoon Hyun <do...@apache.org> wrote:
> Absolutely!
>
> On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org> wrote:
>
>> It sounds good to me.
>>
>> Also remember 'if it doesn't happen on the mailing list, it doesn't
>> happen at Apache'. Please read the below mailing list thread, saying
>> what we must keep.
>>
>>
>> http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
>>
>> Best regards,
>> Hyunsik
>>
>> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org>
>> wrote:
>> > Today we have a Tajo regional meetup in Seoul. What about discussing this
>> > issue in detail there?
>> >
>> > Of course, we should post the result here, too.
>> >
>> > Warmly,
>> > Dongjoon
>> >
>> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
>> >
>> >> The major issues looks good to me for 0.11.0 release
>> >> Thank you.
>> >>
>> >> -Jinho
>> >> Best regards
>> >>
>> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
>> <javascript:;>
>> >> >:
>> >>
>> >> > Hi folks,
>> >> >
>> >> > In order to share milestones with you guys and concentrate our effort
>> >> > on the next release, we need to discuss the next roadmap.
>> >> > Particularly, I'd like to share our direction with new contributors
>> >> > due to the growing number of contributors.
>> >> >
>> >> > As far as I know, the following major issues seem to be resolved in
>> time.
>> >> >
>> >> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721
>> )
>> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>> >> > * Resource allocation should be fine grained (TAJO-1397)
>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>> >> > * Python UDF (TAJO-1344)
>> >> >
>> >> > The above issues probably can be included in 0.11 release. If there
>> >> > are missed issues, please let me know them.
>> >> >
>> >> >
>> >> > Besides, the following feature issues may be on our roadmap:
>> >> >
>> >> > * Multi-tenancy query scheduler (TAJO-540)
>> >> > * More SQL features (scalar subquery, ...)
>> >> > * Decimal type support
>> >> > * Scalar subquery
>> >> > * OLAP features (rollup, drill down, cube, ..)
>> >> > * More rewrite rules (lots of issues like Unnesting of Nested
>> Subqueries,
>> >> > ...)
>> >> > * Make storage handler more pluggable
>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
>> >> > * CREATE FUNCTION statement support
>> >> > * CREATE TYPE statement support
>> >> > * ....
>> >> >
>> >> > Most of them are not assigned as far as I know. In addition, there are
>> >> > many performance issues. I'll describe them later.
>> >> >
>> >> > Anyway, I would be pleasure if we task about what issues you are
>> >> > considering for 0.11 release or after that. I'm looking forward to
>> >> > hearing you guys' feedback.
>> >> >
>> >> >
>> >> > Best regards,
>> >> > Hyunsik
>> >> >
>> >>
>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@apache.org>.
Absolutely!
On Thu, Mar 19, 2015 at 7:32 AM, Hyunsik Choi <hy...@apache.org> wrote:
> It sounds good to me.
>
> Also remember 'if it doesn't happen on the mailing list, it doesn't
> happen at Apache'. Please read the below mailing list thread, saying
> what we must keep.
>
>
> http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
>
> Best regards,
> Hyunsik
>
> On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
> > Today we have a Tajo regional meetup in Seoul. What about discussing this
> > issue in detail there?
> >
> > Of course, we should post the result here, too.
> >
> > Warmly,
> > Dongjoon
> >
> > On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
> >
> >> The major issues looks good to me for 0.11.0 release
> >> Thank you.
> >>
> >> -Jinho
> >> Best regards
> >>
> >> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org
> <javascript:;>
> >> >:
> >>
> >> > Hi folks,
> >> >
> >> > In order to share milestones with you guys and concentrate our effort
> >> > on the next release, we need to discuss the next roadmap.
> >> > Particularly, I'd like to share our direction with new contributors
> >> > due to the growing number of contributors.
> >> >
> >> > As far as I know, the following major issues seem to be resolved in
> time.
> >> >
> >> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721
> )
> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> >> > * Resource allocation should be fine grained (TAJO-1397)
> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> >> > * Python UDF (TAJO-1344)
> >> >
> >> > The above issues probably can be included in 0.11 release. If there
> >> > are missed issues, please let me know them.
> >> >
> >> >
> >> > Besides, the following feature issues may be on our roadmap:
> >> >
> >> > * Multi-tenancy query scheduler (TAJO-540)
> >> > * More SQL features (scalar subquery, ...)
> >> > * Decimal type support
> >> > * Scalar subquery
> >> > * OLAP features (rollup, drill down, cube, ..)
> >> > * More rewrite rules (lots of issues like Unnesting of Nested
> Subqueries,
> >> > ...)
> >> > * Make storage handler more pluggable
> >> > * Better failure handling of tasks and nodes (TAJO-1214)
> >> > * CREATE FUNCTION statement support
> >> > * CREATE TYPE statement support
> >> > * ....
> >> >
> >> > Most of them are not assigned as far as I know. In addition, there are
> >> > many performance issues. I'll describe them later.
> >> >
> >> > Anyway, I would be pleasure if we task about what issues you are
> >> > considering for 0.11 release or after that. I'm looking forward to
> >> > hearing you guys' feedback.
> >> >
> >> >
> >> > Best regards,
> >> > Hyunsik
> >> >
> >>
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
It sounds good to me.
Also remember 'if it doesn't happen on the mailing list, it doesn't
happen at Apache'. Please read the below mailing list thread, saying
what we must keep.
http://mail-archives.apache.org/mod_mbox/community-dev/201303.mbox/%3CCAJwFCa0CfjFGq5NcG7GNSPEZjg1hvy3NO-5_KfPd2ZXvc-SHKg@mail.gmail.com%3E
Best regards,
Hyunsik
On Wed, Mar 18, 2015 at 2:51 PM, Dongjoon Hyun <do...@apache.org> wrote:
> Today we have a Tajo regional meetup in Seoul. What about discussing this
> issue in detail there?
>
> Of course, we should post the result here, too.
>
> Warmly,
> Dongjoon
>
> On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
>
>> The major issues looks good to me for 0.11.0 release
>> Thank you.
>>
>> -Jinho
>> Best regards
>>
>> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org <javascript:;>
>> >:
>>
>> > Hi folks,
>> >
>> > In order to share milestones with you guys and concentrate our effort
>> > on the next release, we need to discuss the next roadmap.
>> > Particularly, I'd like to share our direction with new contributors
>> > due to the growing number of contributors.
>> >
>> > As far as I know, the following major issues seem to be resolved in time.
>> >
>> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
>> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>> > * Resource allocation should be fine grained (TAJO-1397)
>> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>> > * Python UDF (TAJO-1344)
>> >
>> > The above issues probably can be included in 0.11 release. If there
>> > are missed issues, please let me know them.
>> >
>> >
>> > Besides, the following feature issues may be on our roadmap:
>> >
>> > * Multi-tenancy query scheduler (TAJO-540)
>> > * More SQL features (scalar subquery, ...)
>> > * Decimal type support
>> > * Scalar subquery
>> > * OLAP features (rollup, drill down, cube, ..)
>> > * More rewrite rules (lots of issues like Unnesting of Nested Subqueries,
>> > ...)
>> > * Make storage handler more pluggable
>> > * Better failure handling of tasks and nodes (TAJO-1214)
>> > * CREATE FUNCTION statement support
>> > * CREATE TYPE statement support
>> > * ....
>> >
>> > Most of them are not assigned as far as I know. In addition, there are
>> > many performance issues. I'll describe them later.
>> >
>> > Anyway, I would be pleasure if we task about what issues you are
>> > considering for 0.11 release or after that. I'm looking forward to
>> > hearing you guys' feedback.
>> >
>> >
>> > Best regards,
>> > Hyunsik
>> >
>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@apache.org>.
Today we have a Tajo regional meetup in Seoul. What about discussing this
issue in detail there?
Of course, we should post the result here, too.
Warmly,
Dongjoon
On Tuesday, March 17, 2015, Jinho Kim <jh...@apache.org> wrote:
> The major issues looks good to me for 0.11.0 release
> Thank you.
>
> -Jinho
> Best regards
>
> 2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hyunsik@apache.org <javascript:;>
> >:
>
> > Hi folks,
> >
> > In order to share milestones with you guys and concentrate our effort
> > on the next release, we need to discuss the next roadmap.
> > Particularly, I'd like to share our direction with new contributors
> > due to the growing number of contributors.
> >
> > As far as I know, the following major issues seem to be resolved in time.
> >
> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> > * Resource allocation should be fine grained (TAJO-1397)
> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> > * Python UDF (TAJO-1344)
> >
> > The above issues probably can be included in 0.11 release. If there
> > are missed issues, please let me know them.
> >
> >
> > Besides, the following feature issues may be on our roadmap:
> >
> > * Multi-tenancy query scheduler (TAJO-540)
> > * More SQL features (scalar subquery, ...)
> > * Decimal type support
> > * Scalar subquery
> > * OLAP features (rollup, drill down, cube, ..)
> > * More rewrite rules (lots of issues like Unnesting of Nested Subqueries,
> > ...)
> > * Make storage handler more pluggable
> > * Better failure handling of tasks and nodes (TAJO-1214)
> > * CREATE FUNCTION statement support
> > * CREATE TYPE statement support
> > * ....
> >
> > Most of them are not assigned as far as I know. In addition, there are
> > many performance issues. I'll describe them later.
> >
> > Anyway, I would be pleasure if we task about what issues you are
> > considering for 0.11 release or after that. I'm looking forward to
> > hearing you guys' feedback.
> >
> >
> > Best regards,
> > Hyunsik
> >
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Jinho Kim <jh...@apache.org>.
The major issues looks good to me for 0.11.0 release
Thank you.
-Jinho
Best regards
2015-03-16 20:13 GMT+09:00 Hyunsik Choi <hy...@apache.org>:
> Hi folks,
>
> In order to share milestones with you guys and concentrate our effort
> on the next release, we need to discuss the next roadmap.
> Particularly, I'd like to share our direction with new contributors
> due to the growing number of contributors.
>
> As far as I know, the following major issues seem to be resolved in time.
>
> * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
> * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> * Resource allocation should be fine grained (TAJO-1397)
> * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> * Python UDF (TAJO-1344)
>
> The above issues probably can be included in 0.11 release. If there
> are missed issues, please let me know them.
>
>
> Besides, the following feature issues may be on our roadmap:
>
> * Multi-tenancy query scheduler (TAJO-540)
> * More SQL features (scalar subquery, ...)
> * Decimal type support
> * Scalar subquery
> * OLAP features (rollup, drill down, cube, ..)
> * More rewrite rules (lots of issues like Unnesting of Nested Subqueries,
> ...)
> * Make storage handler more pluggable
> * Better failure handling of tasks and nodes (TAJO-1214)
> * CREATE FUNCTION statement support
> * CREATE TYPE statement support
> * ....
>
> Most of them are not assigned as far as I know. In addition, there are
> many performance issues. I'll describe them later.
>
> Anyway, I would be pleasure if we task about what issues you are
> considering for 0.11 release or after that. I'm looking forward to
> hearing you guys' feedback.
>
>
> Best regards,
> Hyunsik
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
Hi Jihoon,
Thank you for your suggestion. Indexing feature is very impressive to me.
I agree with your suggestion.
BTW, in my view, it is still an experimental feature due to the
following reasons:
* only CSV file format works with this index.
* Index size still is too large.
* Incremental update is not supported.
I also think that they will be resolved later.
But, like codegen feature we need to tag 'experimental' to the index feature
in documentation and others because they are still challenges.
Best regards,
Hyunsik
On Mon, Mar 16, 2015 at 4:36 AM, Jihoon Son <ji...@apache.org> wrote:
> I'd like to merge the index_support branch into the master.
> I think it would be enough to be merged if two more issues are resolved.
>
> Sincerely,
> Jihoon
>
> On Mon, Mar 16, 2015 at 8:31 PM Jaehwa Jung <bl...@apache.org> wrote:
>
>> Hi Hyunsik
>>
>> I totally agree with you.
>>
>> And if possible, could you add some examples for pluggable storage? For
>> example, we're already working it such as, kafka, elasticsearch, cassandra.
>>
>> Cheers
>> Jaehwa
>> 2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
>>
>> > Hi folks,
>> >
>> > In order to share milestones with you guys and concentrate our effort
>> > on the next release, we need to discuss the next roadmap.
>> > Particularly, I'd like to share our direction with new contributors
>> > due to the growing number of contributors.
>> >
>> > As far as I know, the following major issues seem to be resolved in time.
>> >
>> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
>> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>> > * Resource allocation should be fine grained (TAJO-1397)
>> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>> > * Python UDF (TAJO-1344)
>> >
>> > The above issues probably can be included in 0.11 release. If there
>> > are missed issues, please let me know them.
>> >
>> >
>> > Besides, the following feature issues may be on our roadmap:
>> >
>> > * Multi-tenancy query scheduler (TAJO-540)
>> > * More SQL features (scalar subquery, ...)
>> > * Decimal type support
>> > * Scalar subquery
>> > * OLAP features (rollup, drill down, cube, ..)
>> > * More rewrite rules (lots of issues like Unnesting of Nested Subqueries,
>> > ...)
>> > * Make storage handler more pluggable
>> > * Better failure handling of tasks and nodes (TAJO-1214)
>> > * CREATE FUNCTION statement support
>> > * CREATE TYPE statement support
>> > * ....
>> >
>> > Most of them are not assigned as far as I know. In addition, there are
>> > many performance issues. I'll describe them later.
>> >
>> > Anyway, I would be pleasure if we task about what issues you are
>> > considering for 0.11 release or after that. I'm looking forward to
>> > hearing you guys' feedback.
>> >
>> >
>> > Best regards,
>> > Hyunsik
>> >
>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
- Is there a candidate release date for 0.11.0?
(As a user, I love the way if Ububtu OS.)
The release date depends on our progress. We usually do not decide
release date. When scheduled issues are completed, we usually discuss
release. Of course, we can release minor release for bug fixes between
major releases.
- Cloud you give us a guideline to distinguish 0.11.0 and 0.12.0 feature?
(Focus? or Importance?)
You can expect what features will be included in 0.11 from this
discussion. I'm not sure the detailed features of 0.12 release. I
hazard a guess that 0.12 will have the followings:
* full-fledged multi-tenancy scheduler
* full support of nested complex data types: array, union, or ...
* more mature support of operations and expressions for nested
complex data types: flatten, ...
* generic storages, more plugins of it, and query optimization support
Actually, they are more mature versions of our current working issues
that I took. There may be additional issues on which other
contributors are working.
Best regards,
Hyunsik
On Mon, Mar 16, 2015 at 3:02 PM, Dongjoon Hyun <do...@gmail.com> wrote:
> Thank you very much for your confirmation.
>
> I have three more questions.
>
> - Is there a candidate release date for 0.11.0?
> (As a user, I love the way if Ububtu OS.)
> - Cloud you give us a guideline to distinguish 0.11.0 and 0.12.0 feature?
> (Focus? or Importance?)
>
> Warmly,
> Dongjoon.
>
>
>
> On Mar 17, 2015, at 6:48 AM, Hyunsik Choi <hy...@apache.org> wrote:
>
> Hi Dongjoon,
>
> Of course, we will update the roadmap wiki after our discussion.
>
> Thank you for suggesting features. All features you mentioned are on
> our roadmap.
> If someone started these issues and can finish in time, they can be
> included in 0.11 release.
>
> Some issues look in progress. I checked the issues you mentioned, and
> I leave some comments here.
> * Keuntae just started to TAJO-921.
> * TPC-DS unit tests look useful. We can add them to our unit tests in
> order to verify the correctness of those kinds of queries. BTW, there
> is no jira for it, and we need to create it.
> * WITH clause : Any progress is invisible. we need to create it.
> Someone should start it not lately.
>
> Yarn support is also on our roadmap. Please refer to TAJO-773.
> Regarding authentication and security, we need to investigate it and
> its around stuff more.
> Sentry and Ranger may be some candidates. Besides, we can choose other choice.
>
> Best regards,
> Hyunsik
>
>> On Mon, Mar 16, 2015 at 5:23 AM, Dongjoon Hyun <do...@apache.org> wrote:
>> Hi, Hyunsik.
>>
>> As a user and a member of community, thank you for all your efforts to show
>> us a predictable Tajo Vision. At the end of this discussion, could you
>> update Tajo Roadmap Wiki as a result? That will lead us in a more
>> synergetic way. (
>> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap )
>>
>> To all,
>> Is it possible to include the following features to be completed at this
>> time.
>> 1. WITH clause support (for TPC-DS)
>> I expect the subquery feature will enable this easier than now.
>> 2. STDDEV_POP, STDDEV_SAMP support (for TPC-DS)
>> https://issues.apache.org/jira/browse/TAJO-921
>> 3. Unit Tests with TPC-DS
>> For more stable Tajo, I think Tajo need more testcases.
>>
>> By the way, according to the Tajo Roadmap wiki, I think @hyunsik mentioned
>> almost items there except the followings.
>> - YARN Support
>> - Security (Basic User Authentication) - Apache Sentry??
>>
>> Does Tajo have a plan for these two items?
>>
>> Best regards,
>> Dongjoon.
>>
>>> On Mon, Mar 16, 2015 at 8:41 PM, Jihoon Son <ji...@apache.org> wrote:
>>>
>>> I mean, it will be possible to include the index feature to 0.11 release.
>>>
>>> Best,
>>> Jihoon
>>> 2015년 3월 16일 (월) 오후 8:37, Jihoon Son <ji...@apache.org>님이 작성:
>>>
>>>> I'd like to merge the index_support branch into the master.
>>>> I think it would be enough to be merged if two more issues are resolved.
>>>>
>>>> Sincerely,
>>>> Jihoon
>>>>
>>>>
>>>>> On Mon, Mar 16, 2015 at 8:31 PM Jaehwa Jung <bl...@apache.org> wrote:
>>>>>
>>>>> Hi Hyunsik
>>>>>
>>>>> I totally agree with you.
>>>>>
>>>>> And if possible, could you add some examples for pluggable storage? For
>>>>> example, we're already working it such as, kafka, elasticsearch,
>>>>> cassandra.
>>>>>
>>>>> Cheers
>>>>> Jaehwa
>>>>> 2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
>>>>>
>>>>>> Hi folks,
>>>>>>
>>>>>> In order to share milestones with you guys and concentrate our effort
>>>>>> on the next release, we need to discuss the next roadmap.
>>>>>> Particularly, I'd like to share our direction with new contributors
>>>>>> due to the growing number of contributors.
>>>>>>
>>>>>> As far as I know, the following major issues seem to be resolved in
>>>>> time.
>>>>>>
>>>>>> * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721
>>> )
>>>>>> * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>>>>>> * Resource allocation should be fine grained (TAJO-1397)
>>>>>> * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>>>>>> * Python UDF (TAJO-1344)
>>>>>>
>>>>>> The above issues probably can be included in 0.11 release. If there
>>>>>> are missed issues, please let me know them.
>>>>>>
>>>>>>
>>>>>> Besides, the following feature issues may be on our roadmap:
>>>>>>
>>>>>> * Multi-tenancy query scheduler (TAJO-540)
>>>>>> * More SQL features (scalar subquery, ...)
>>>>>> * Decimal type support
>>>>>> * Scalar subquery
>>>>>> * OLAP features (rollup, drill down, cube, ..)
>>>>>> * More rewrite rules (lots of issues like Unnesting of Nested
>>>>> Subqueries,
>>>>>> ...)
>>>>>> * Make storage handler more pluggable
>>>>>> * Better failure handling of tasks and nodes (TAJO-1214)
>>>>>> * CREATE FUNCTION statement support
>>>>>> * CREATE TYPE statement support
>>>>>> * ....
>>>>>>
>>>>>> Most of them are not assigned as far as I know. In addition, there are
>>>>>> many performance issues. I'll describe them later.
>>>>>>
>>>>>> Anyway, I would be pleasure if we task about what issues you are
>>>>>> considering for 0.11 release or after that. I'm looking forward to
>>>>>> hearing you guys' feedback.
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>> Hyunsik
>>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@gmail.com>.
Thank you very much for your confirmation.
I have three more questions.
- Is there a candidate release date for 0.11.0?
(As a user, I love the way if Ububtu OS.)
- Cloud you give us a guideline to distinguish 0.11.0 and 0.12.0 feature?
(Focus? or Importance?)
Warmly,
Dongjoon.
On Mar 17, 2015, at 6:48 AM, Hyunsik Choi <hy...@apache.org> wrote:
Hi Dongjoon,
Of course, we will update the roadmap wiki after our discussion.
Thank you for suggesting features. All features you mentioned are on
our roadmap.
If someone started these issues and can finish in time, they can be
included in 0.11 release.
Some issues look in progress. I checked the issues you mentioned, and
I leave some comments here.
* Keuntae just started to TAJO-921.
* TPC-DS unit tests look useful. We can add them to our unit tests in
order to verify the correctness of those kinds of queries. BTW, there
is no jira for it, and we need to create it.
* WITH clause : Any progress is invisible. we need to create it.
Someone should start it not lately.
Yarn support is also on our roadmap. Please refer to TAJO-773.
Regarding authentication and security, we need to investigate it and
its around stuff more.
Sentry and Ranger may be some candidates. Besides, we can choose other choice.
Best regards,
Hyunsik
> On Mon, Mar 16, 2015 at 5:23 AM, Dongjoon Hyun <do...@apache.org> wrote:
> Hi, Hyunsik.
>
> As a user and a member of community, thank you for all your efforts to show
> us a predictable Tajo Vision. At the end of this discussion, could you
> update Tajo Roadmap Wiki as a result? That will lead us in a more
> synergetic way. (
> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap )
>
> To all,
> Is it possible to include the following features to be completed at this
> time.
> 1. WITH clause support (for TPC-DS)
> I expect the subquery feature will enable this easier than now.
> 2. STDDEV_POP, STDDEV_SAMP support (for TPC-DS)
> https://issues.apache.org/jira/browse/TAJO-921
> 3. Unit Tests with TPC-DS
> For more stable Tajo, I think Tajo need more testcases.
>
> By the way, according to the Tajo Roadmap wiki, I think @hyunsik mentioned
> almost items there except the followings.
> - YARN Support
> - Security (Basic User Authentication) - Apache Sentry??
>
> Does Tajo have a plan for these two items?
>
> Best regards,
> Dongjoon.
>
>> On Mon, Mar 16, 2015 at 8:41 PM, Jihoon Son <ji...@apache.org> wrote:
>>
>> I mean, it will be possible to include the index feature to 0.11 release.
>>
>> Best,
>> Jihoon
>> 2015년 3월 16일 (월) 오후 8:37, Jihoon Son <ji...@apache.org>님이 작성:
>>
>>> I'd like to merge the index_support branch into the master.
>>> I think it would be enough to be merged if two more issues are resolved.
>>>
>>> Sincerely,
>>> Jihoon
>>>
>>>
>>>> On Mon, Mar 16, 2015 at 8:31 PM Jaehwa Jung <bl...@apache.org> wrote:
>>>>
>>>> Hi Hyunsik
>>>>
>>>> I totally agree with you.
>>>>
>>>> And if possible, could you add some examples for pluggable storage? For
>>>> example, we're already working it such as, kafka, elasticsearch,
>>>> cassandra.
>>>>
>>>> Cheers
>>>> Jaehwa
>>>> 2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
>>>>
>>>>> Hi folks,
>>>>>
>>>>> In order to share milestones with you guys and concentrate our effort
>>>>> on the next release, we need to discuss the next roadmap.
>>>>> Particularly, I'd like to share our direction with new contributors
>>>>> due to the growing number of contributors.
>>>>>
>>>>> As far as I know, the following major issues seem to be resolved in
>>>> time.
>>>>>
>>>>> * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721
>> )
>>>>> * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>>>>> * Resource allocation should be fine grained (TAJO-1397)
>>>>> * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>>>>> * Python UDF (TAJO-1344)
>>>>>
>>>>> The above issues probably can be included in 0.11 release. If there
>>>>> are missed issues, please let me know them.
>>>>>
>>>>>
>>>>> Besides, the following feature issues may be on our roadmap:
>>>>>
>>>>> * Multi-tenancy query scheduler (TAJO-540)
>>>>> * More SQL features (scalar subquery, ...)
>>>>> * Decimal type support
>>>>> * Scalar subquery
>>>>> * OLAP features (rollup, drill down, cube, ..)
>>>>> * More rewrite rules (lots of issues like Unnesting of Nested
>>>> Subqueries,
>>>>> ...)
>>>>> * Make storage handler more pluggable
>>>>> * Better failure handling of tasks and nodes (TAJO-1214)
>>>>> * CREATE FUNCTION statement support
>>>>> * CREATE TYPE statement support
>>>>> * ....
>>>>>
>>>>> Most of them are not assigned as far as I know. In addition, there are
>>>>> many performance issues. I'll describe them later.
>>>>>
>>>>> Anyway, I would be pleasure if we task about what issues you are
>>>>> considering for 0.11 release or after that. I'm looking forward to
>>>>> hearing you guys' feedback.
>>>>>
>>>>>
>>>>> Best regards,
>>>>> Hyunsik
>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Hyunsik Choi <hy...@apache.org>.
Hi Dongjoon,
Of course, we will update the roadmap wiki after our discussion.
Thank you for suggesting features. All features you mentioned are on
our roadmap.
If someone started these issues and can finish in time, they can be
included in 0.11 release.
Some issues look in progress. I checked the issues you mentioned, and
I leave some comments here.
* Keuntae just started to TAJO-921.
* TPC-DS unit tests look useful. We can add them to our unit tests in
order to verify the correctness of those kinds of queries. BTW, there
is no jira for it, and we need to create it.
* WITH clause : Any progress is invisible. we need to create it.
Someone should start it not lately.
Yarn support is also on our roadmap. Please refer to TAJO-773.
Regarding authentication and security, we need to investigate it and
its around stuff more.
Sentry and Ranger may be some candidates. Besides, we can choose other choice.
Best regards,
Hyunsik
On Mon, Mar 16, 2015 at 5:23 AM, Dongjoon Hyun <do...@apache.org> wrote:
> Hi, Hyunsik.
>
> As a user and a member of community, thank you for all your efforts to show
> us a predictable Tajo Vision. At the end of this discussion, could you
> update Tajo Roadmap Wiki as a result? That will lead us in a more
> synergetic way. (
> https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap )
>
> To all,
> Is it possible to include the following features to be completed at this
> time.
> 1. WITH clause support (for TPC-DS)
> I expect the subquery feature will enable this easier than now.
> 2. STDDEV_POP, STDDEV_SAMP support (for TPC-DS)
> https://issues.apache.org/jira/browse/TAJO-921
> 3. Unit Tests with TPC-DS
> For more stable Tajo, I think Tajo need more testcases.
>
> By the way, according to the Tajo Roadmap wiki, I think @hyunsik mentioned
> almost items there except the followings.
> - YARN Support
> - Security (Basic User Authentication) - Apache Sentry??
>
> Does Tajo have a plan for these two items?
>
> Best regards,
> Dongjoon.
>
> On Mon, Mar 16, 2015 at 8:41 PM, Jihoon Son <ji...@apache.org> wrote:
>
>> I mean, it will be possible to include the index feature to 0.11 release.
>>
>> Best,
>> Jihoon
>> 2015년 3월 16일 (월) 오후 8:37, Jihoon Son <ji...@apache.org>님이 작성:
>>
>> > I'd like to merge the index_support branch into the master.
>> > I think it would be enough to be merged if two more issues are resolved.
>> >
>> > Sincerely,
>> > Jihoon
>> >
>> >
>> > On Mon, Mar 16, 2015 at 8:31 PM Jaehwa Jung <bl...@apache.org> wrote:
>> >
>> >> Hi Hyunsik
>> >>
>> >> I totally agree with you.
>> >>
>> >> And if possible, could you add some examples for pluggable storage? For
>> >> example, we're already working it such as, kafka, elasticsearch,
>> >> cassandra.
>> >>
>> >> Cheers
>> >> Jaehwa
>> >> 2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
>> >>
>> >> > Hi folks,
>> >> >
>> >> > In order to share milestones with you guys and concentrate our effort
>> >> > on the next release, we need to discuss the next roadmap.
>> >> > Particularly, I'd like to share our direction with new contributors
>> >> > due to the growing number of contributors.
>> >> >
>> >> > As far as I know, the following major issues seem to be resolved in
>> >> time.
>> >> >
>> >> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721
>> )
>> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>> >> > * Resource allocation should be fine grained (TAJO-1397)
>> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>> >> > * Python UDF (TAJO-1344)
>> >> >
>> >> > The above issues probably can be included in 0.11 release. If there
>> >> > are missed issues, please let me know them.
>> >> >
>> >> >
>> >> > Besides, the following feature issues may be on our roadmap:
>> >> >
>> >> > * Multi-tenancy query scheduler (TAJO-540)
>> >> > * More SQL features (scalar subquery, ...)
>> >> > * Decimal type support
>> >> > * Scalar subquery
>> >> > * OLAP features (rollup, drill down, cube, ..)
>> >> > * More rewrite rules (lots of issues like Unnesting of Nested
>> >> Subqueries,
>> >> > ...)
>> >> > * Make storage handler more pluggable
>> >> > * Better failure handling of tasks and nodes (TAJO-1214)
>> >> > * CREATE FUNCTION statement support
>> >> > * CREATE TYPE statement support
>> >> > * ....
>> >> >
>> >> > Most of them are not assigned as far as I know. In addition, there are
>> >> > many performance issues. I'll describe them later.
>> >> >
>> >> > Anyway, I would be pleasure if we task about what issues you are
>> >> > considering for 0.11 release or after that. I'm looking forward to
>> >> > hearing you guys' feedback.
>> >> >
>> >> >
>> >> > Best regards,
>> >> > Hyunsik
>> >> >
>> >>
>> >
>>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Dongjoon Hyun <do...@apache.org>.
Hi, Hyunsik.
As a user and a member of community, thank you for all your efforts to show
us a predictable Tajo Vision. At the end of this discussion, could you
update Tajo Roadmap Wiki as a result? That will lead us in a more
synergetic way. (
https://cwiki.apache.org/confluence/display/TAJO/Tajo+Roadmap )
To all,
Is it possible to include the following features to be completed at this
time.
1. WITH clause support (for TPC-DS)
I expect the subquery feature will enable this easier than now.
2. STDDEV_POP, STDDEV_SAMP support (for TPC-DS)
https://issues.apache.org/jira/browse/TAJO-921
3. Unit Tests with TPC-DS
For more stable Tajo, I think Tajo need more testcases.
By the way, according to the Tajo Roadmap wiki, I think @hyunsik mentioned
almost items there except the followings.
- YARN Support
- Security (Basic User Authentication) - Apache Sentry??
Does Tajo have a plan for these two items?
Best regards,
Dongjoon.
On Mon, Mar 16, 2015 at 8:41 PM, Jihoon Son <ji...@apache.org> wrote:
> I mean, it will be possible to include the index feature to 0.11 release.
>
> Best,
> Jihoon
> 2015년 3월 16일 (월) 오후 8:37, Jihoon Son <ji...@apache.org>님이 작성:
>
> > I'd like to merge the index_support branch into the master.
> > I think it would be enough to be merged if two more issues are resolved.
> >
> > Sincerely,
> > Jihoon
> >
> >
> > On Mon, Mar 16, 2015 at 8:31 PM Jaehwa Jung <bl...@apache.org> wrote:
> >
> >> Hi Hyunsik
> >>
> >> I totally agree with you.
> >>
> >> And if possible, could you add some examples for pluggable storage? For
> >> example, we're already working it such as, kafka, elasticsearch,
> >> cassandra.
> >>
> >> Cheers
> >> Jaehwa
> >> 2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
> >>
> >> > Hi folks,
> >> >
> >> > In order to share milestones with you guys and concentrate our effort
> >> > on the next release, we need to discuss the next roadmap.
> >> > Particularly, I'd like to share our direction with new contributors
> >> > due to the growing number of contributors.
> >> >
> >> > As far as I know, the following major issues seem to be resolved in
> >> time.
> >> >
> >> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721
> )
> >> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> >> > * Resource allocation should be fine grained (TAJO-1397)
> >> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> >> > * Python UDF (TAJO-1344)
> >> >
> >> > The above issues probably can be included in 0.11 release. If there
> >> > are missed issues, please let me know them.
> >> >
> >> >
> >> > Besides, the following feature issues may be on our roadmap:
> >> >
> >> > * Multi-tenancy query scheduler (TAJO-540)
> >> > * More SQL features (scalar subquery, ...)
> >> > * Decimal type support
> >> > * Scalar subquery
> >> > * OLAP features (rollup, drill down, cube, ..)
> >> > * More rewrite rules (lots of issues like Unnesting of Nested
> >> Subqueries,
> >> > ...)
> >> > * Make storage handler more pluggable
> >> > * Better failure handling of tasks and nodes (TAJO-1214)
> >> > * CREATE FUNCTION statement support
> >> > * CREATE TYPE statement support
> >> > * ....
> >> >
> >> > Most of them are not assigned as far as I know. In addition, there are
> >> > many performance issues. I'll describe them later.
> >> >
> >> > Anyway, I would be pleasure if we task about what issues you are
> >> > considering for 0.11 release or after that. I'm looking forward to
> >> > hearing you guys' feedback.
> >> >
> >> >
> >> > Best regards,
> >> > Hyunsik
> >> >
> >>
> >
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Jihoon Son <ji...@apache.org>.
I mean, it will be possible to include the index feature to 0.11 release.
Best,
Jihoon
2015년 3월 16일 (월) 오후 8:37, Jihoon Son <ji...@apache.org>님이 작성:
> I'd like to merge the index_support branch into the master.
> I think it would be enough to be merged if two more issues are resolved.
>
> Sincerely,
> Jihoon
>
>
> On Mon, Mar 16, 2015 at 8:31 PM Jaehwa Jung <bl...@apache.org> wrote:
>
>> Hi Hyunsik
>>
>> I totally agree with you.
>>
>> And if possible, could you add some examples for pluggable storage? For
>> example, we're already working it such as, kafka, elasticsearch,
>> cassandra.
>>
>> Cheers
>> Jaehwa
>> 2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
>>
>> > Hi folks,
>> >
>> > In order to share milestones with you guys and concentrate our effort
>> > on the next release, we need to discuss the next roadmap.
>> > Particularly, I'd like to share our direction with new contributors
>> > due to the growing number of contributors.
>> >
>> > As far as I know, the following major issues seem to be resolved in
>> time.
>> >
>> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
>> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
>> > * Resource allocation should be fine grained (TAJO-1397)
>> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
>> > * Python UDF (TAJO-1344)
>> >
>> > The above issues probably can be included in 0.11 release. If there
>> > are missed issues, please let me know them.
>> >
>> >
>> > Besides, the following feature issues may be on our roadmap:
>> >
>> > * Multi-tenancy query scheduler (TAJO-540)
>> > * More SQL features (scalar subquery, ...)
>> > * Decimal type support
>> > * Scalar subquery
>> > * OLAP features (rollup, drill down, cube, ..)
>> > * More rewrite rules (lots of issues like Unnesting of Nested
>> Subqueries,
>> > ...)
>> > * Make storage handler more pluggable
>> > * Better failure handling of tasks and nodes (TAJO-1214)
>> > * CREATE FUNCTION statement support
>> > * CREATE TYPE statement support
>> > * ....
>> >
>> > Most of them are not assigned as far as I know. In addition, there are
>> > many performance issues. I'll describe them later.
>> >
>> > Anyway, I would be pleasure if we task about what issues you are
>> > considering for 0.11 release or after that. I'm looking forward to
>> > hearing you guys' feedback.
>> >
>> >
>> > Best regards,
>> > Hyunsik
>> >
>>
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Jihoon Son <ji...@apache.org>.
I'd like to merge the index_support branch into the master.
I think it would be enough to be merged if two more issues are resolved.
Sincerely,
Jihoon
On Mon, Mar 16, 2015 at 8:31 PM Jaehwa Jung <bl...@apache.org> wrote:
> Hi Hyunsik
>
> I totally agree with you.
>
> And if possible, could you add some examples for pluggable storage? For
> example, we're already working it such as, kafka, elasticsearch, cassandra.
>
> Cheers
> Jaehwa
> 2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
>
> > Hi folks,
> >
> > In order to share milestones with you guys and concentrate our effort
> > on the next release, we need to discuss the next roadmap.
> > Particularly, I'd like to share our direction with new contributors
> > due to the growing number of contributors.
> >
> > As far as I know, the following major issues seem to be resolved in time.
> >
> > * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
> > * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> > * Resource allocation should be fine grained (TAJO-1397)
> > * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> > * Python UDF (TAJO-1344)
> >
> > The above issues probably can be included in 0.11 release. If there
> > are missed issues, please let me know them.
> >
> >
> > Besides, the following feature issues may be on our roadmap:
> >
> > * Multi-tenancy query scheduler (TAJO-540)
> > * More SQL features (scalar subquery, ...)
> > * Decimal type support
> > * Scalar subquery
> > * OLAP features (rollup, drill down, cube, ..)
> > * More rewrite rules (lots of issues like Unnesting of Nested Subqueries,
> > ...)
> > * Make storage handler more pluggable
> > * Better failure handling of tasks and nodes (TAJO-1214)
> > * CREATE FUNCTION statement support
> > * CREATE TYPE statement support
> > * ....
> >
> > Most of them are not assigned as far as I know. In addition, there are
> > many performance issues. I'll describe them later.
> >
> > Anyway, I would be pleasure if we task about what issues you are
> > considering for 0.11 release or after that. I'm looking forward to
> > hearing you guys' feedback.
> >
> >
> > Best regards,
> > Hyunsik
> >
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Jaehwa Jung <bl...@apache.org>.
Hi Hyunsik
I totally agree with you.
And if possible, could you add some examples for pluggable storage? For
example, we're already working it such as, kafka, elasticsearch, cassandra.
Cheers
Jaehwa
2015. 3. 16. 오후 8:13에 "Hyunsik Choi" <hy...@apache.org>님이 작성:
> Hi folks,
>
> In order to share milestones with you guys and concentrate our effort
> on the next release, we need to discuss the next roadmap.
> Particularly, I'd like to share our direction with new contributors
> due to the growing number of contributors.
>
> As far as I know, the following major issues seem to be resolved in time.
>
> * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
> * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> * Resource allocation should be fine grained (TAJO-1397)
> * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> * Python UDF (TAJO-1344)
>
> The above issues probably can be included in 0.11 release. If there
> are missed issues, please let me know them.
>
>
> Besides, the following feature issues may be on our roadmap:
>
> * Multi-tenancy query scheduler (TAJO-540)
> * More SQL features (scalar subquery, ...)
> * Decimal type support
> * Scalar subquery
> * OLAP features (rollup, drill down, cube, ..)
> * More rewrite rules (lots of issues like Unnesting of Nested Subqueries,
> ...)
> * Make storage handler more pluggable
> * Better failure handling of tasks and nodes (TAJO-1214)
> * CREATE FUNCTION statement support
> * CREATE TYPE statement support
> * ....
>
> Most of them are not assigned as far as I know. In addition, there are
> many performance issues. I'll describe them later.
>
> Anyway, I would be pleasure if we task about what issues you are
> considering for 0.11 release or after that. I'm looking forward to
> hearing you guys' feedback.
>
>
> Best regards,
> Hyunsik
>
Re: [DISCUSSION] Beyond 0.10.0 release
Posted by Azuryy Yu <az...@gmail.com>.
Thanks Hyunsik,
I will look through these features and hope can do something in future.
IMO, if Tajo supports multi-tenants and security, then we are truely better
than Impala according to my performance testing.
On Mon, Mar 16, 2015 at 7:13 PM, Hyunsik Choi <hy...@apache.org> wrote:
> Hi folks,
>
> In order to share milestones with you guys and concentrate our effort
> on the next release, we need to discuss the next roadmap.
> Particularly, I'd like to share our direction with new contributors
> due to the growing number of contributors.
>
> As far as I know, the following major issues seem to be resolved in time.
>
> * Nested complex type (https://issues.apache.org/jira/browse/TAJO-721)
> * in subquery (https://issues.apache.org/jira/browse/TAJO-680)
> * Resource allocation should be fine grained (TAJO-1397)
> * ALTER TABLE ADD/DROP PARTITION statement (TAJO-744)
> * Python UDF (TAJO-1344)
>
> The above issues probably can be included in 0.11 release. If there
> are missed issues, please let me know them.
>
>
> Besides, the following feature issues may be on our roadmap:
>
> * Multi-tenancy query scheduler (TAJO-540)
> * More SQL features (scalar subquery, ...)
> * Decimal type support
> * Scalar subquery
> * OLAP features (rollup, drill down, cube, ..)
> * More rewrite rules (lots of issues like Unnesting of Nested Subqueries,
> ...)
> * Make storage handler more pluggable
> * Better failure handling of tasks and nodes (TAJO-1214)
> * CREATE FUNCTION statement support
> * CREATE TYPE statement support
> * ....
>
> Most of them are not assigned as far as I know. In addition, there are
> many performance issues. I'll describe them later.
>
> Anyway, I would be pleasure if we task about what issues you are
> considering for 0.11 release or after that. I'm looking forward to
> hearing you guys' feedback.
>
>
> Best regards,
> Hyunsik
>