You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Khai Tran (JIRA)" <ji...@apache.org> on 2019/06/07 18:21:00 UTC
[jira] [Created] (CALCITE-3122) Contribution request: converting
Pig Latin scripts into Calcite logical plan
Khai Tran created CALCITE-3122:
----------------------------------
Summary: Contribution request: converting Pig Latin scripts into Calcite logical plan
Key: CALCITE-3122
URL: https://issues.apache.org/jira/browse/CALCITE-3122
Project: Calcite
Issue Type: New Feature
Components: core, piglet
Reporter: Khai Tran
We create an internal Calcite repo at LinkedIn and develop APIs to parse any Pig Latin scripts into Calcite logical plan. The code was tested in nearly ~1000 Pig scripts written at LinkedIn.
Changes:
1. piglet: main conversion code live there, include:
* APIs to convert any Pig scripts into RelNode plans or SQL statements
* Use Pig Grunt parser to parse Pig Latin scripts into Pig logical plan (DAGs)
* Convert Pig schemas into RelDatatype
* Traverse through Pig expression plan and convert Pig expressions into RexNodes
* Map some basic Pig UDFs to Calcite SQL operators
* Build Calcite UDFs for any other Pig UDFs, including UDFs written in both Java and Python
* Traverse (DFS) through Pig logical plans to convert each Pig logical nodes to RelNodes
* Have an optimizer rule to optimize Pig group/cogroup into Aggregate operators
2. core:
* Implement other RelNode in Rel2Sql so that Pig can be translated into SQL
* Other minor changes in a few other classes to make Pig to Calcite works
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)