Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 062EF175E0 for ; Tue, 17 Mar 2015 01:21:46 +0000 (UTC) Received: (qmail 39724 invoked by uid 500); 17 Mar 2015 01:21:45 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 39679 invoked by uid 500); 17 Mar 2015 01:21:45 -0000 Mailing-List: contact dev-help@tajo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.apache.org Delivered-To: mailing list dev@tajo.apache.org Received: (qmail 39668 invoked by uid 99); 17 Mar 2015 01:21:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 01:21:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of azuryyyu@gmail.com designates 209.85.216.172 as permitted sender) Received: from [209.85.216.172] (HELO mail-qc0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 01:21:40 +0000 Received: by qcbkw5 with SMTP id kw5so61113470qcb.2 for ; Mon, 16 Mar 2015 18:19:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=hPXh4BTIoQG5tLoFO4TtTSYftu0IOornUiJlKLwkJkk=; b=REkTeSclsZ89/Mwq/FiUJ5BO71+bT9djZFZ8YDqh3fXSShOyJpgjtCkPb366pD/fPD cvC6ywvCavljuyjo8i8br2jdAyUM0pzynMWz0jG4wo99wKMZ79vNHSuRFYdFtUO4EPwC nz6aGQrN6LKehc9IJba8vuBTnrcqQuTvrBbSz3bkNZoNZ/BhIagCVve1wBI9i+7s024Y nGKJToATVq7J6C2TMk0ILqhYCa0W/IS7JVzeDNnYG52VXshGPlquUo+Gp5QmfPuTJ+Pc 87ZkCQDjoYadna65qFctkB8dEH1MJ/7tQ/lkIc4SLdHCietMhS4bAfix+WZGHMq1ijUT 6Wiw== MIME-Version: 1.0 X-Received: by 10.55.31.10 with SMTP id f10mr93042759qkf.58.1426555189587; Mon, 16 Mar 2015 18:19:49 -0700 (PDT) Received: by 10.140.83.201 with HTTP; Mon, 16 Mar 2015 18:19:49 -0700 (PDT) In-Reply-To: References: Date: Tue, 17 Mar 2015 09:19:49 +0800 Message-ID: Subject: Re: [DISCUSSION] Beyond 0.10.0 release From: Azuryy Yu To: "dev@tajo.apache.org" Content-Type: multipart/alternative; boundary=001a1147ebda53f2f6051171c385 X-Virus-Checked: Checked by ClamAV on apache.org --001a1147ebda53f2f6051171c385 Content-Type: text/plain; charset=UTF-8 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 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 > --001a1147ebda53f2f6051171c385--