Lai Zhou created CALCITE-2741:
-
Summary: extend the native enummerable implemention of calcite to
support Hive SQL
Key: CALCITE-2741
URL: https://issues.apache.org/jira/browse/CALCITE-2741
Project:
I have no strong opinion since I am not using the adapter.
However, I have a small question regarding option 2.
Is the query still going to be inefficient if the user adds the IS NOT NULL
predicate?
If yes, then I probably option 1 would be the best option for the moment.
Otherwise, I don't find
Hello!
My use case is sessionizing raw events without an aggregation function.
Approximate code that I tried out:
SELECT ARRAY_AGG(ROW(...))
FROM ...
GROUP BY SESSION(...)
(followed by UNNEST to get the raw events, tagged with session info, back
out into a stream)
I get a parser error on the
> Is the query still going to be inefficient if the user adds the IS NOT
NULL predicate?
It will be efficient. For explicit null check aggregates can be pushed to
ES since sentinel will never be used.
> Otherwise, I don't find it very problematic to expect the users to right
their queries
Hi all,
It’s my first time to send emails to Calcite developers. It’s a really good
project and many projects benefit from it.
Now I’ve encountered a problem about the subsets for MATCH_RECOGNIZE in
thetestMatchRecognizeSubset1() testing. From the results, I can tell
that"subset stdn =
