Mailing-List: contact dev-help@tajo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAFu6yH1dd1qsBv3+dMOYAdcOkuwtCNdxiAv-C+sRHNsFhsBu2g@mail.gmail.com>
References: 
 <CAFu6yH3NUCqhUSOwVz4o829zLKJOebY9On54OXWksp0W56erEQ@mail.gmail.com>
	<CAM=XDd_1uMg_NRL2TF6-SgL8QKKh-a-3nUK-tHzF2rN8K8AhuA@mail.gmail.com>
	<CAFu6yH0DVOjjyNbTUtOAv52yYrEWWDovcFSNKGUzc89Y3su7hQ@mail.gmail.com>
	<CAM=XDd9vEkr1TcC8tpUXn4pYBS+k3kfooUt_z1gc91TeVAk8Mg@mail.gmail.com>
	<CAFu6yH3fjzLKRoBsZ17GztpkpwxsYbOtCr=GWCkJEG90myaQww@mail.gmail.com>
	<CAM=XDd_f5s5qXLjXuLTGzWL5TO7YkvgVjYg9rtYUAtyVkz+pmg@mail.gmail.com>
	<CAFu6yH1dd1qsBv3+dMOYAdcOkuwtCNdxiAv-C+sRHNsFhsBu2g@mail.gmail.com>
Date: Sat, 21 Mar 2015 21:51:25 -0700
Message-ID: 
 <CAM=XDd95wf-wZQsS-HJ4E+5LSLQAEPLaXVnEaFXPZ9tLYQ9n-g@mail.gmail.com>
Subject: Re: [DISCUSSION] Hi-Speed Tajo: Fastest Hadoop DW
From: Hyunsik Choi <hyunsik@apache.org>
To: "dev@tajo.apache.org" <dev@tajo.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

TPC-DS is just a benchmark, and it is not test sets. For just test
cases, why should we aim at TPC-DS? They are not proper as well as are
overkill for this purpose.

> For the TPC-DS, Tajo PMC doesn't make any committment in Roadmap already.

> TPC-DS does not mean anything to TAJO roadmap.

They are NOT TRUE. As you already know, WITH, IN/EXIST subquery, and
scalar subquery are already on our roadmap. If they are supported,
most of TPC-DS queries will work naturally. I'm concerning with your
intension, saying we do not consider TPC-DS.

On Sat, Mar 21, 2015 at 4:38 PM, Dongjoon Hyun <dongjoon@apache.org> wrote:
> Hyunsik, TPC-DS is not important. It's just a way to see Tajo Maturity as=
 a
> SQL engine. TPC-DS does not mean anything to TAJO roadmap.
>
> More specifically, the importance is the same with TPC-H, however Tajo
> handled TPC-H well now, doesn't it? So, we need just another testsuite to
> see how Tajo handle SQL(including WITH/IN/EXISTS) clause well. I think yo=
u
> agree that in TAJO-1410.
>
> TPC defines
> - TPC-H: TPC-H is an ad-hoc, decision support benchmark.
> - TPC-DS: TPC Benchmark=E2=84=A2DS (TPC-DS): The New Decision Support Ben=
chmark
> Standard
>
> In these days, TPC-DS is replacing the ancient TPC-H from real site
> customers.
> The main reason is based on the lack of TPC-H. TPC-H became a basic level=
.
>
> Could you tell me if you have some other testcases in mind, except TPC-DS=
?
>
> Dongjoon.
>
> On Sun, Mar 22, 2015 at 3:58 AM, Hyunsik Choi <hyunsik@apache.org> wrote:
>
>> Could you tell me why you think TPC-DS is important?
>>
>> On Saturday, March 21, 2015, Dongjoon Hyun <dongjoon@apache.org> wrote:
>>
>> > Oh, that was an expression of my regret about my weak pull-requests.
>> There
>> > exists no offence. It's a duty. I hope you didn't waste your time much
>> due
>> > to my stupid learning cost.
>> >
>> > After Hyunsik's direct advice, I have studied Tajo Jira more and
>> understand
>> > what you mean slightly more. Now I understand many speedup issues, e.g=
.
>> > offheap-based scanner, zero-copy physical layer processing. For newbie=
s
>> > like me, we need more men like you.
>> >
>> > For the TPC-DS, Tajo PMC doesn't make any committment in Roadmap
>> already. I
>> > respect the current roadmap. You need not worry about that. It's my
>> > personal hope as I mentioned before in this mailing list. Here is more
>> > recent another report about TPC-DS. (It's consistent with the report
>> shared
>> > by Hyunsik.)
>> >
>> >
>> >
>> https://developer.ibm.com/hadoop/blog/2014/12/02/big-sql-3-0-hadoop-ds-b=
enchmark-performance-isnt-everything/
>> >
>> >
>> > Thank you all.
>> >
>> > Warmly,
>> > Dongjoon.
>> >
>>