Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <7EE7D91AE4DB0C40B1A1F87489D87CBC2A36F04A@at-bp-embx-05.theice.com>
References: <7EE7D91AE4DB0C40B1A1F87489D87CBC2A36F04A@at-bp-embx-05.theice.com>
From: Paul Guo <paulguo@gmail.com>
Date: Thu, 12 Jan 2017 10:15:04 +0800
Message-ID: <CABQrizcUVgJVr-cyuRKkKQJjouokTRPtofGAS8a-9P=4kFCGEg@mail.gmail.com>
Subject: Re: Different storage backends in HAWQ?
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a114401261357f00545dc4934
archived-at: Thu, 12 Jan 2017 02:15:10 -0000

--001a114401261357f00545dc4934
Content-Type: text/plain; charset=UTF-8

HAWQ supports row oriented format also (AO Table). For block storage &
posix fs, I suspect you could use gpdb since gpdb uses local storage though
probably a bit additional work is needed. For object storage (e.g. S3
interface), this is an interesting topic. There have been a JIRA for this
though there are some debates about better solutions.

HAWQ-823 Amazon S3 External Table Support
https://issues.apache.org/jira/browse/HAWQ-823


2017-01-11 23:14 GMT+08:00 Dmitry Buzolin <Dmitry.Buzolin@theice.com>:

> Since HAWQ only depends on Hadoop and Parquet as a columnar format. I
> would like to propose having Hawq having pluggable storage backends.
> Hadoop is already supported but there is Ceph storage backend which offers
> standard Posix compliant file system, object and a block storage. Ceph is
> also is location aware and written in C++. I believe this is more important
> than porting HAWQ to windows. Your thoughts?
>
> Thanks,
> Dmitry.
>
> ________________________________
>
> This message may contain confidential information and is intended for
> specific recipients unless explicitly noted otherwise. If you have reason
> to believe you are not an intended recipient of this message, please delete
> it and notify the sender. This message may not represent the opinion of
> Intercontinental Exchange, Inc. (ICE), its subsidiaries or affiliates, and
> does not constitute a contract or guarantee. Unencrypted electronic mail is
> not secure and the recipient of this message is expected to provide
> safeguards from viruses and pursue alternate means of communication where
> privacy or a binding message is desired.
>

--001a114401261357f00545dc4934--