Unfortunately this requires a patch to Calcite.
I am testing the patch right now.

So far changes are to RelFieldTrimmer, RexUtil, ProjectRemoveRule.

On Tue, Jan 27, 2015 at 10:55 AM, John Pullokkaran <
[email protected]> wrote:

> Many of Hive issues seems to be the result of CALCITE-92.
>
> I don’t think there is anything wrong with the patch itself, but it breaks
> Hive’s usage of Calcite (due to Calcite OP tree getting converted back to
> Hive AST).
>
> I am going to try disabling it in Hive’s usage of Calcite; will update
> soon.
>
> John
>
> On Jan 27, 2015, at 9:38 AM, Julian Hyde <[email protected]<mailto:
> [email protected]>> wrote:
>
> On Mon, Jan 26, 2015 at 10:11 PM, John Pullokkaran
> <[email protected]<mailto:[email protected]>> wrote:
>
> On Mon, Jan 26, 2015 at 1:42 PM, John Pullokkaran <
> [email protected]<mailto:[email protected]>> wrote:
>
> We seems to have issues with union, subquery, and constants.
>
> Currently we are debugging these to find more details.
>
> Would update EOB today.
>
> So far 2 issues been discovered with Calcite RC; CALCITE-570, CALCITE-571.
>
> John,
>
> Is that your final list? I have a fix for
> https://issues.apache.org/jira/browse/CALCITE-570, am working on
> https://issues.apache.org/jira/browse/CALCITE-571. I intend to produce
> a new RC including these and
> https://issues.apache.org/jira/browse/CALCITE-567 and
> https://issues.apache.org/jira/browse/CALCITE-568 (both issues that
> Vladimir found in RC1). If your list is final RC2 could be as early as
> end of today.
>
> When there is an RC2, would it help to have a few days to review it
> before I start a vote?
>
> Julian
>
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Reply via email to