[ 
https://issues.apache.org/jira/browse/CALCITE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882531#comment-16882531
 ] 

Khai Tran commented on CALCITE-3122:
------------------------------------

Thanks a lot for the review. I will try to address them all, but first I have 
question for the second bullet "Can you make {{RelOptCluster.planner}} final 
again?"



First I need to do that because I need to use a new planner to optimize an 
existing logical plan, as each node in the plan is assigned to a previous 
planner, the optimizer will complain that the node belongs to a different 
planner. So there is a need to reset the planner for all nodes in the plan and 
resetting through RelOptCluster is the easiest way (the other way is to use 
RelShuttle to create a plan with the new planner, which I dont think we 
currently have).

On the other hand, I saw the pattern of mutable fields in RelOptCluster, so 
just wonder if we can do the same for planner. Otherwise, I will need to write 
the Shuttle to reset planner for all nodes in the plan.

> Convert 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
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to