[POC][KERNEL][VARIANT] Extract variant fields to directly return to the connector #8
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
richardc-db
force-pushed
the
kernel_read_variant
branch
from
844cb0b to
5722e8d
Compare
richardc-db
force-pushed
the
kernel_read_variant
branch
from
3860375 to
ddc75dc
Compare
richardc-db
force-pushed
the
kernel_read_variant
branch
2 times, most recently
from
c06180d to
6a879b5
Compare
richardc-db
force-pushed
the
kernel_read_variant
branch
from
6a879b5 to
2032fa3
Compare
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.
Which Delta project/connector is this regarding?
Description
POC that shows kernel implementation of extracting variant child fields to return directly to the connector so the connector does not need to understand how to decode variants.
note this PR doesn't actually implement
variant_getto return the correct field. Instead it just returns a dummy value. This PR is meant to show how connectors could use the new APIHow was this patch tested?
Does this PR introduce any user-facing changes?