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: <CADvk=GZfzDoejzB9JRsLSn2nJszHe3it1pyHDmMdMkNY5s8DYA@mail.gmail.com>
References: <CADvk=GZfzDoejzB9JRsLSn2nJszHe3it1pyHDmMdMkNY5s8DYA@mail.gmail.com>
From: Shivram Mani <shivram.mani@gmail.com>
Date: Mon, 3 Oct 2016 16:17:04 -0700
Message-ID: <CALpJHBCag=mAzo-GTXRfuQTmS2xGSSkhK2OPWMfk9ULfHv40Yg@mail.gmail.com>
Subject: Re: PXF Plugin
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c025ca9018c6053dfe2591
archived-at: Mon, 03 Oct 2016 23:17:31 -0000

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

Apologies for the delayed response.
Apart from updating DataType class, there are additional updates on the
HAWQ/PXF bridge code in C to support more data types (pxffilters.c)
You can refer to https://github.com/apache/incubator-hawq/pull/913/files
which apart from other functionality, we've also added support to handle
timestamp type.

On Fri, Sep 23, 2016 at 12:07 PM, Kyle Dunn <kdunn@pivotal.io> wrote:

> Hello-
>
> I'm looking at extending PXF for a new data source and noticed only a
> subset of the HAWQ-supported primitive datatypes are implemented in PXF. Is
> this as trivial as mapping a type to the corresponding OID in
> "api/io/DataType.java" or is there something more I'm missing?
>
> Thanks,
>
> -Kyle
> --
> *Kyle Dunn | Data Engineering | Pivotal*
> Direct: 303.905.3171 <3039053171> | Email: kdunn@pivotal.io
>


-- 
shivram mani

--001a11c025ca9018c6053dfe2591--