You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Julian Feinauer (JIRA)" <ji...@apache.org> on 2018/10/25 12:10:00 UTC

[jira] [Created] (CALCITE-2640) Support for SQL on Timeseries / Traces

Julian Feinauer created CALCITE-2640:
----------------------------------------

             Summary: Support for SQL on Timeseries / Traces
                 Key: CALCITE-2640
                 URL: https://issues.apache.org/jira/browse/CALCITE-2640
             Project: Calcite
          Issue Type: New Feature
            Reporter: Julian Feinauer
            Assignee: Julian Hyde


When working with time series data, e.g., from IoT devices, traces or other sources there is often the need for analysis on "transients". This means that it is important to compare values with their neighbors (i.e., prev / next) to detect jumps or changes of bits.

This is possible with the MATCH_RECOGNIZE functionality from SQL 2016 but perhaps there is also the possibility for a "sensible" extension to SQL (like Streaming SQL is) to support these use cases with a "less technical" syntax. Others also use a pseudo-SQL syntax to do "more time series focussed" things (like use GROUP BY to do time averaging in IinfluxDB). See [1] for InfluxDBs SQL-like QL InfluxQL.
And it would be better to have a "more standardized" way of the interaction between SQL and timeseries than several SQL-like DSLs.

There was also a discussion on the list, see [2].

[1] https://docs.influxdata.com/influxdb/v1.6/query_language/
[2] https://lists.apache.org/thread.html/250575a56165851ab55351b90a26eaa30e84d5bbe2b31203daaaefb9@%3Cdev.calcite.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)