Jungtaek Lim created CALCITE-1387:
-
Summary: CAST(ITEM() as INTEGER) throws RuntimeException in
Runtime when return value of ITEM() is null
Key: CALCITE-1387
URL: https://issues.apache.org/jira/browse/CALCITE-1387
Jungtaek Lim created CALCITE-1386:
-
Summary: ITEM operator seems to ignore the value type of
collection and assign the value to Object
Key: CALCITE-1386
URL: https://issues.apache.org/jira/browse/CALCITE-1386
Regarding 1 and 2: these sound like bugs. Can you please log a JIRA case for
each? If you can supply a test case, even better.
Regarding 3. I checked the SQL standard, and the required behavior is to throw
an exception. (Maybe ArrayIndexOutOfBoundsException isn’t the best exception to
throw.)
Have you considered the sliding window, which is already part of standard SQL?
We propose to support it in streaming SQL also. Here is an example:
SELECT orderId, price, AVG(price) OVER (ORDER BY orderTime ROWS 5 PRECEDING)
FROM Orders
(This is a non-streaming query, but you can add the STR
I think you should just be able to override getStatistic() in your table
implementations and return a Statistic object that has an accurate row count.
The table scan should compute its cost from that, and uses 100d as a default
IIRC.
> On Sep 25, 2016, at 1:56 PM, Γιώργος Θεοδωράκης
> wrote:
Hi,
First of all let me introduce myself - My name is Radu Tudoran and I am working
in the field of Big Data processing with a high focus on streaming and more
recently in the area of SQL.
I wanted to raise a question/proposal for discussion in the community:
Based on our requirements I reali
