I have logged https://issues.apache.org/jira/browse/CALCITE-1021 for the
“upgrade” part of this issue. When we come to consensus on shading that could
be another JIRA case.
Drill, Hive, Samza, Storm, and other stakeholders: Please chime in on that
issue if a Jackson upgrade would break you.
Ju
For the avatica (client) jar, it's meant to be a single distributable
artifact, but I could see value in providing both a shaded and
non-shaded jar, letting the user decide which one they want.
It will force us to be much clearer about what the dependency needs of
the Avatica client are.
Ted
The “coupling” is not for performance. Each AST node (SqlNode) contains a
position so that we can give a good error message, including the exact position
of the error, when there is a validation error. This important if you are
running a SQL statement that is more than a few lines long.
SqlPars
dear,
I have a question,why the parser and operator Tree are coupled，like this:
SqlNode(SqlParserPos pos) {
Util.pre(pos != null, "pos != null");
this.pos = pos;
}
Because we pass the variable pos，it lead to the couple。
I develped a parser use antlr，and hope the parse and symantec
We wrote a tech blog on our work.
Interested can check here:
http://www.hcltech.com/blogs/engineering-and-rd-services/olap-cubing-big-data
We may rephrase few things in the blog next week. But this will give you
the general direction if our approach.
Hi Julian!
Thanks for the explanation. We'll definitely go with embedding Calcite for
now.
As long as DAGs are supported it is fine is the costs are double counted.
In most cases, that probably affects only the absolute cost estimate, and
the relative ranking among plans is still good.
We'll loo
Hi,
Perhaps I didn't look hard enough but I can't find examples of using map in
a where clause. The list archives don't contain any and the first few pages
of google are a bust as well. I did find one example in the select clause
but it didn't include much detail.
I'd like to do a couple of thing
