[ https://issues.apache.org/jira/browse/CALCITE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912743#comment-16912743 ]
Khai Tran commented on CALCITE-3122: ------------------------------------ [~julianhyde] Your commit may not solve the problem. Issue is from this: if we set `planner = PigRelPlanner.createPlanner(builder.getCluster().getPlanner(), rules)`, then all the tests would fail with this exception: `java.lang.AssertionError: Relational expression LogicalUnion#106 belongs to a different planner than is currently being used.java.lang.AssertionError: Relational expression LogicalUnion#106 belongs to a different planner than is currently being used. at org.apache.calcite.plan.volcano.VolcanoPlanner.registerImpl(VolcanoPlanner.java:1633)` I dont know why we need that check, but that's the root of all issues: ` if (rel.getCluster().getPlanner() != this) { throw new AssertionError("Relational expression " + rel + " belongs to a different planner than is currently being used."); }` > 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 > Assignee: Julian Hyde > Priority: Major > Labels: pull-request-available > Fix For: 1.21.0 > > 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 (v8.3.2#803003)