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 AD04A10E91 for ; Tue, 10 Mar 2015 01:58:47 +0000 (UTC) Received: (qmail 4792 invoked by uid 500); 10 Mar 2015 01:58:47 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 4753 invoked by uid 500); 10 Mar 2015 01:58:47 -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 4742 invoked by uid 99); 10 Mar 2015 01:58:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2015 01:58:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.220.49] (HELO mail-pa0-f49.google.com) (209.85.220.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2015 01:58:21 +0000 Received: by pabli10 with SMTP id li10so77204786pab.13 for ; Mon, 09 Mar 2015 18:57:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=b0uWz0TNxiX9GrTWV0vDWrPpqshbjg0jweZI9KXx4Gg=; b=QWB4oHa8gybqAFTSfP/2f5dOwUMXsFk+DUNF0RCwuz3KmEGtzUotB8AzofDXf7QP4x XeJ/o8w95An+BxbcHOCpiza8AK08V8DMAExn31/2aSePEY4IVKnI+ZxZG6b8Xqwz3aaZ z4XsAWqoY7ykjmc1GdUdw1kZnXIkSC1Q7TEys14DxM2G52XEq6D8UI9Aly/ulYaCZ2MY JiwhANQu6D+4vgX0r7Ssj2l+1iEYGdAqjQE5boT+p9VTm7yOSyuU7jYKzKwgftLiuATN UEhV3mg32CdSmcnIcaVxSvOdb8nTZYGrkP0RfY/z+odDhM30ZD0cRHKsx8r/wTqsy8GJ fkVQ== X-Gm-Message-State: ALoCoQmVSdrVOUhwEZj17bK+tHA67XO7fMq4e7lC7nzfKOfRmcOkcCQnRZ0zdCeHLXi4YgeJeE7D X-Received: by 10.70.131.15 with SMTP id oi15mr59712509pdb.161.1425952677056; Mon, 09 Mar 2015 18:57:57 -0700 (PDT) Received: from [192.168.0.18] ([211.63.142.65]) by mx.google.com with ESMTPSA id fx13sm21317712pdb.7.2015.03.09.18.57.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Mar 2015 18:57:55 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_625CEE0D-4543-41F4-8428-6556D8F61C28" Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: [jira] [Commented] (TAJO-337) Generic StorageManager to provide common storage methods From: yshan In-Reply-To: Date: Tue, 10 Mar 2015 10:57:53 +0900 Cc: issues@tajo.incubator.apache.org Message-Id: References: To: dev@tajo.apache.org X-Mailer: Apple Mail (2.1993) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_625CEE0D-4543-41F4-8428-6556D8F61C28 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=euc-kr Good. I eagerly anticipate the doc. Thank you :) -- Yeon-su Han / yshan@gruter.com Gruter, Inc., R&D Team=20 www.gruter.com Enjoy Connecting > 2015. 3. 10., =BF=C0=C0=FC 9:39, Hyunsik Choi (JIRA) = =C0=DB=BC=BA: >=20 >=20 > [ = https://issues.apache.org/jira/browse/TAJO-337?page=3Dcom.atlassian.jira.p= lugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14353981#c= omment-14353981 ]=20 >=20 > Hyunsik Choi commented on TAJO-337: > ----------------------------------- >=20 > Currently, I'm writing the design draft about how I achieve this = feature. I'll share the doc soon. >=20 >> Generic StorageManager to provide common storage methods >> -------------------------------------------------------- >>=20 >> Key: TAJO-337 >> URL: https://issues.apache.org/jira/browse/TAJO-337 >> Project: Tajo >> Issue Type: Improvement >> Components: catalog, storage >> Reporter: Hyunsik Choi >> Assignee: Hyunsik Choi >>=20 >> Currently, Tajo uses HDFS as a primary storage. But, as a data = warehouse system, Tajo should easily support various data sources. >> For this, I propose a generic storage handler interface that provides = common storage methods as follows: >> * splitting input data >> * locality >> * accessing catalog (if providing) >> * creating a table >> * removing a table >> * adding default table properties and validating properties >> * committing, rollback, and clean up output tables >> * getting table physical information like table volumes and others >> * managing connection pool for connection-based storages >> * adding storage-specified rewrite rules >> * adding hooks for query phases >> * physical properties like instant random access, indexible, read = throughput, and write throughput >=20 >=20 >=20 > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) --Apple-Mail=_625CEE0D-4543-41F4-8428-6556D8F61C28--