You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@iotdb.apache.org by GitBox <gi...@apache.org> on 2022/12/08 16:32:34 UTC
[GitHub] [iotdb] marisuki opened a new pull request, #8389: Algebra
marisuki opened a new pull request, #8389:
URL: https://github.com/apache/iotdb/pull/8389
##Description
This is the baseline udf implementations to query time-series on various data types.
The benchmark project is github.com/thssdb/algebra for recurrence.
The baseline aims to obtain the time for loading and merging all data ahead of any filterings and optimizations.
###Content1
Time-series queries:
(Q-S1) Selection contains 2 types: by (closed/open) time range and value, benchmarked by ClosedRange/Value and OpenRange/Value, input 1d time-series, out: 1d.
(Q-S2) Projection: ClosedRange with 2-d time-series in, 1d out.
(Q-S3) Merge: Merge 2 series with a pivot of concatenated ranges.
(Q-S4) Time equality join: ClosedRange, 2d in
(Q-S5) Aggregation by time-based sliding window: AggRWindow
(Q-A1) Sampling over time: Sample, fixed ranged window, taking 1 tuple.
(Q-A2) Generalized projection: series conversion, in: 1d time-series, conversion function f;
(Q-A3) Time equality alignment: ClosedRange query, input: nd-series
###Content2: support operations with temporal tables
Temporal queries:
(Q-T1) Sliding window aggregation: AggCWindow, count-based sliding window,
(Q-T2) Pattern matching: PatternRWindow, in: pattern series and series to match.
###Content3: support operations with relational tables
(Q-R2) Time similarity join: SimJoin, join 2 series with tolerance.
(Q-R3) Series-temporal join: RelJoinTemporal, input: 1d series + temporal table, match corresponding events.
(Q-R4) Generalized aggregation: AggEvent, group by event and aggregation.
(Q-R5) Time similarity alignment: SimJoin, input: n-d time series.
<!--
In each section, please describe design decisions made, including:
- Choice of algorithms
- Behavioral aspects. What configuration values are acceptable? How are corner cases and error
conditions handled, such as when there are insufficient resources?
- Class organization and design (how the logic is split between classes, inheritance, composition,
design patterns)
- Method organization and design (how the logic is split between methods, parameters and return types)
- Naming (class, method, API, configuration, HTTP endpoint, names of emitted metrics)
-->
<!-- It's good to describe an alternative design (or mention an alternative name) for every design
(or naming) decision point and compare the alternatives with the designs that you've implemented
(or the names you've chosen) to highlight the advantages of the chosen designs and names. -->
<!-- If there was a discussion of the design of the feature implemented in this PR elsewhere
(e. g. a "Proposal" issue, any other issue, or a thread in the development mailing list),
link to that discussion from this PR description and explain what have changed in your final design
compared to your original proposal or the consensus version in the end of the discussion.
If something hasn't changed since the original discussion, you can omit a detailed discussion of
those aspects of the design here, perhaps apart from brief mentioning for the sake of readability
of this PR description. -->
<!-- Some of the aspects mentioned above may be omitted for simple and small changes. -->
<hr>
This PR has:
- [x] been self-reviewed.
- [x] added documentation for new or modified features or behaviors.
<!-- Check the items by putting "x" in the brackets for the done things. Not all of these items
apply to every PR. Remove the items which are not done or not relevant to the PR. None of the items
from the checklist above are strictly necessary, but it would be very helpful if you at least
self-review the PR. -->
<hr>
##### Key changed/added classes (or packages if there are too many classes) in this PR
The udf classes for queries involving different data types.
It includes all files inside the package of org.apache.iotdb.library.query.*.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [iotdb] liuminghui233 merged pull request #8389: [research/algebra] To include UDF functions for queries on different data types
Posted by GitBox <gi...@apache.org>.
liuminghui233 merged PR #8389:
URL: https://github.com/apache/iotdb/pull/8389
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org