Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable Clear-break semantics for range queries #6136

Open
teh-cmc opened this issue Apr 26, 2024 · 0 comments
Open

Configurable Clear-break semantics for range queries #6136

teh-cmc opened this issue Apr 26, 2024 · 0 comments
Labels
🔩 data model 🔍 re_query affects re_query itself user-request This is a pressing issue for one of our users

Comments

@teh-cmc
Copy link
Member

teh-cmc commented Apr 26, 2024

Today, range queries go through their data range without any second thought: if some piece of data was Cleared in the middle of the range, it simply yields an empty array at this specific timestamp, which the system doing the query is free to handle as it pleases.
Only the plot view actually does something with that empty array today: it breaks the curve in half at this timestamp.

It would be nice if range queries could be configured to behave in different ways in the face of Clear events, directly at the query layer, rather than on a per-system/per-view basis.

Consider this dataset:

t=0 [##]
t=1 [####]
t=2 <clear>
t=3 [###]
t=4 [#]

One possibility is to just yield an empty array, like we do today:

Range(0, 4) = [(t=0 [##]), (t=1 [####]), (t=2 []), (t=3 [###]), (t=4 [#])]

Another possibility would be to break the range at the latest sight of a Clear event:

Range(0, 4) = [(t=3 [###]), (t=4 [#])]

In that way the range query effectively behaves as a kind of temporal accumulator, that can be reset by the user at any time.


More food for thought of that nature in this thread: https://discord.com/channels/1062300748202921994/1075873257124810852/1233429218441035879

@teh-cmc teh-cmc added 🔍 re_query affects re_query itself user-request This is a pressing issue for one of our users 🔩 data model labels Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔩 data model 🔍 re_query affects re_query itself user-request This is a pressing issue for one of our users
Projects
None yet
Development

No branches or pull requests

1 participant