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 163C810ED5 for ; Tue, 11 Nov 2014 00:37:03 +0000 (UTC) Received: (qmail 35370 invoked by uid 500); 11 Nov 2014 00:37:02 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 35326 invoked by uid 500); 11 Nov 2014 00:37:02 -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 35316 invoked by uid 99); 11 Nov 2014 00:37:02 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Nov 2014 00:37:02 +0000 Received: from localhost (HELO mail-qa0-f46.google.com) (127.0.0.1) (smtp-auth username hyunsik, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Nov 2014 00:37:02 +0000 Received: by mail-qa0-f46.google.com with SMTP id n8so6152783qaq.33 for ; Mon, 10 Nov 2014 16:37:00 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.84.71 with SMTP id k65mr45676815qgd.76.1415666220412; Mon, 10 Nov 2014 16:37:00 -0800 (PST) Received: by 10.96.196.166 with HTTP; Mon, 10 Nov 2014 16:37:00 -0800 (PST) In-Reply-To: References: Date: Mon, 10 Nov 2014 16:37:00 -0800 Message-ID: Subject: Re: Next roadmap after 0.9.0 release From: Hyunsik Choi To: "dev@tajo.apache.org" Content-Type: text/plain; charset=UTF-8 Recently, Hyoungjun worked hbase storage, and he has refactored storage module to be more general. With this work, we can support more storage types. Especially, I believe that JDBC-based storages (i.e., RDBMS as a storage) would be helpful to complement Tajo's nature which does not support interactive insert/update storage. Also, Tajo makes good use of indexing feature of RDBMSs. Best regards, Hyunsik On Mon, Nov 10, 2014 at 4:29 PM, Hyunsik Choi wrote: > Currently, Tajo is being incrementally disseminated in users. I have > heard many times the following requests: > > * thin JDBC driver > * Orc file support > * Kerberos > * ODBC > * Multi-tenancy in scheduler > > Probably, we should go the direction by considering the above features. > > Best regards, > Hyunsik > > On Mon, Nov 10, 2014 at 4:23 PM, Hyunsik Choi wrote: >> Hi Jihoon, >> >> 0.9.1 will be an incremental release which includes some bug fixes and >> new minor features. Most of your suggested issues look nice for 0.9.1. >> Additional issues which were already committed to master will be >> naturally included in 0.9.1. But, we need to check if TAJO-982 is >> reasonable. >> >> In my opinion, we can discuss the 0.9.1 soon. >> >> On Mon, Oct 13, 2014 at 11:27 PM, Jihoon Son wrote: >>> Hi Hyunsik, >>> >>> More frequent release sounds great! >>> Here are the notable issues that are currently scheduled for 0.9.1. >>> >>> - TAJO-1095: implement JSON file scanner >>> - TAJO-1026: implement query history persistency manager >>> - TAJO-982: improve fetcher to get multiple shuffle outputs through a >>> request >>> - TAJO-269: change the de/serialization protocol of logical plan of >>> query unit attempt from Json to ProtocolBuffer >>> - TAJO-235, TAJO-233: support oracle and postgresql catalog store >>> >>> IMO, if we resolve the above issues, it would be sufficient for the next >>> release. >>> >>> Thanks! >>> Jihoon >>> >>> >>> 2014-10-13 17:58 GMT+09:00 Hyunsik Choi : >>> >>>> Hi folks, >>>> >>>> I'd like to discuss the next roadmap after 0.9.0 release. Currently, I >>>> already separated 0.9.0 branch from master branch. So, we can feel >>>> free to proceed our work in master branch. >>>> >>>> Because the current Tajo is very stable, it would be great if we >>>> release Tajo more frequently. It will gain more attention from this >>>> field. >>>> >>>> So, I propose that we release 0.9.1 after about one month. I'd like to >>>> hear you guys' opinions. >>>> >>>> Also, let's talk about the roadmap of 0.9.1. >>>> >>>> - Hyunsik >>>>