Hi,
I have also run tests on Hive (after applying the fix in HIVE-9454) using
Calcite-RC1. Many union related tests (e.g. union_remove_8.q) are failing
too with the following stack trace:
2015-01-25 13:18:40,201 ERROR [main]: parse.CalcitePlanner
(CalcitePlanner.java:genOPTree(256)) - CBO failed, skipping CBO.
org.apache.hadoop.hive.ql.parse.SemanticException
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genUnionPlan(SemanticAnalyzer.java:9107)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:9701)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:9722)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:9695)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:9698)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:9722)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:9708)
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.genOPTree(CalcitePlanner.java:248)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:10155)
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:192)
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:224)
at
org.apache.hadoop.hive.ql.parse.ExplainSemanticAnalyzer.analyzeInternal(ExplainSemanticAnalyzer.java:74)
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:224)
...
I've not been able to check the issues into much more detail yet, but it
looks like we have problems on Hive + Calcite RC1 that go beyond cosmetics,
and that should be fixed before pushing the final release. Thus, my vote:
-1 (non-binding).
Thanks,
Jesús
On Sun, Jan 25, 2015 at 6:02 PM, John Pullokkaran <
[email protected]> wrote:
> I tried few of the failing tests with the RC & they seems to be still
> failing.
> I looked in to one of them "subquery_in_having.q".
>
> See the exception stack below:
> java.lang.Exception
> at
>
> org.apache.hadoop.hive.ql.parse.TypeCheckCtx.setError(TypeCheckCtx.java:152)
> at
>
> org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.processQualifiedColRef(TypeCheckProcFactory.java:1001)
> at
>
> org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:1109)
> at
>
> org.apache.hadoop.hive.ql.parse.QBSubQuery$ConjunctAnalyzer.resolveDot(QBSubQuery.java:331)
> at
>
> org.apache.hadoop.hive.ql.parse.QBSubQuery$ConjunctAnalyzer.analyzeExpr(QBSubQuery.java:273)
> at
>
> org.apache.hadoop.hive.ql.parse.QBSubQuery$ConjunctAnalyzer.analyzeExpr(QBSubQuery.java:285)
> at
>
> org.apache.hadoop.hive.ql.parse.QBSubQuery$ConjunctAnalyzer.analyzeConjunct(QBSubQuery.java:315)
> at org.apache.hadoop.hive.ql.parse.QBSubQuery.rewrite(QBSubQuery.java:785)
> at
>
> org.apache.hadoop.hive.ql.parse.QBSubQuery.validateAndRewriteAST(QBSubQuery.java:587)
> at
>
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.genFilterRelNode(CalcitePlanner.java:1366)
> at
>
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.genGBHavingLogicalPlan(CalcitePlanner.java:2662)
> at
>
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.genLogicalPlan(CalcitePlanner.java:2573)
> at
>
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:693)
> at
>
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:660)
> at org.apache.calcite.tools.Frameworks$1.apply(Frameworks.java:109)
>
>
> On Sun, Jan 25, 2015 at 8:53 AM, Julian Hyde <[email protected]>
> wrote:
>
> > Most if not all of those failures are either cosmetic or are plan
> > improvements.
> >
> > Can you provide specifics?
> >
> > Julian
> >
> > > On Jan 25, 2015, at 07:59, John Pullokkaran <
> > [email protected]> wrote:
> > >
> > > I am seeing around 60 failures for Hive with the RC candidate.
> > > In addition to CALCITE-566, there seems to be other issues.
> > >
> > > -1 non binding.
> > >
> > > Thanks
> > > John
> > >
> > >
> > >> On Sat, Jan 24, 2015 at 9:57 PM, Julian Hyde <[email protected]>
> > wrote:
> > >>
> > >> 24 hours left to vote for 1.0 RC1. Please download the release, kick
> > >> the tires, and vote! (Only PPMC votes are binding, but other votes
> > >> help us get to a high-quality release.)
> > >>
> > >> 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.
> >
>
> --
> 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.
>
--
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.
