You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2016/12/23 01:33:58 UTC

[jira] [Updated] (HAWQ-1235) Create a prototype for Calcite running with PXF backend

     [ https://issues.apache.org/jira/browse/HAWQ-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated HAWQ-1235:
-----------------------------------
    Summary: Create a prototype for Calcite running with PXF backend  (was: Created a prototype for Calcite running with PXF backend)

> Create a prototype for Calcite running with PXF backend
> -------------------------------------------------------
>
>                 Key: HAWQ-1235
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1235
>             Project: Apache HAWQ
>          Issue Type: Sub-task
>          Components: PXF
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>
> A possibility of using PXF outside of its original HAWQ use case is pretty exciting. Calcite is also pretty exciting. This JIRA tracks my efforts of making the prototype of the two working together.
> The first goal here could be make PXF available to Apache Calcite
> as a backend (since Calcite itself doesn't deal with storage of data,
> algorithms to process data, and a repository for storing metadata).
> Calcite comes with a demo that allows you to treat a directory
> full of CSV files as a DB (with individual files being tables) and
> I wanted to extend that demo to use PXF reading CSV files from HDFS
> instead:
>   http://calcite.apache.org/docs/tutorial.html
> https://github.com/apache/calcite/tree/master/example/csv/src/main/java/org/apache/calcite/adapter/csv
> Once that is done -- we can grow from there and use Calcite to validate assumptions that exist between HAWQ and PXF



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)