You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support clear semantics in the dataframe API.
Tombstones are never visible to end-users, only their effect.
Like every other Dataframe v2 feature PR, and following recommendations
from @jleibs, this prioritizes convenience of implementation over
everything else, for now.
All clear chunks are fetched, post-processed, and re-injected into the
view contents during init(), and then the streaming join runs as usual
after that.
Static clear semantics can get pretty unhinged, but that's A) not
specific to the dataframe API and B) so extremely niche that our time is
better spent on real-world problems right now:
- #7650
- #7631
---
- Fixes#7495
- Fixes#7414
- Fixes#7468
- Fixes#7493
- DNM: requires #7649
Take this for example:
What would you expect to see in the viewer at
frame=3
?If you guessed "nothing", you're right (although that doesn't seem very useful...):
What about
frame=0..3
?If you guessed "3 points", you're right (although at this point you should be frantically scratching your head already):
Now what if I asked you about
Dataframe(0..3)
? What aboutDataframe(0..3, SparseFill::LatestAtGlobal)
?! 😱Anyway, it's extremely niche, so definitely not the highest prio right now.
The text was updated successfully, but these errors were encountered: