Introduce Lens as a concept for semantic mapping of arbitrary data
#11394
+1,032
−89
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related
-formatting option for redacted values #11383.What
This PR introduces the concept of Lenses as a way to express re-interpretation and manipulation of component columns. This can, for example, be useful to attach Rerun semantics to arbitrary Arrow components that are created when loading MCAP files.
For now, the only way to access the feature is via the
LensesSink, which transforms component columns and then forwards aggregated chunks to the backing sink.Important
Lenses are still a very experimental feature and we expect the API to change a lot in upcoming releases.