[Pulsar IO] Clarify usage of KVRecord on Sinks - #10113
Closed
eolivelli wants to merge 3 commits into
Closed
Conversation
- set the generic type to Record<KeyValue> - let Sinks receive instances of KVRecord in case of KeyValue payload and schema
eolivelli
changed the title
Contributor
Author
|
@tuteng can you please take a look? since you are the author of KVRecord interface |
eolivelli
marked this pull request as ready for review
April 1, 2021 14:58
sijie
requested changes
Apr 1, 2021
| } | ||
| try { | ||
| this.sink.write(new SinkRecord<>(srcRecord, output)); | ||
| SinkRecord sinkRecord; |
Member
There was a problem hiding this comment.
I don't understand why do you need this change here. What is the value for adding a SinkKVRecord? SinkRecord is a wrapper of the output object. The output object can be a KeyValue object.
Contributor
Author
There was a problem hiding this comment.
@sijie
these are the key points:
- on the Source side you use KVRecord for records with a KeyValue payload, this lets you specify the keySchema and the valueSchema, for consistency it is good to have the same situation on the Sink side
- KeyValueSchema is not part of the public api (it is in the impl package), so in theory you cannot get the keySchema and the valueSchema when you are inside a Sink, if we implement KVRecord then you have those schemas
- When we have AutoConsumeSchema that returns a KeyValue object the record.getSchema() is the internal class AutoConsumeSchema, so you cannot still get the keySchema and the valueSchema (this problem is still not present, because we have not merged the Sink<GenericObject patch yet
Contributor
Author
There was a problem hiding this comment.
@sijie the alternative is:
- make KeyValueSchema part of the "public" API (or add an interface on the "api" package)
- hide "AutoConsumeSchema" in the Sink side and make Record#getSchema() return the current KeyValueSchema
but this alternative is not good because:
- we are going to add a new API to represent KeyValueSchema, but we already have KVRecord
- we are changing the behaviour of the Sink, not returning AutoConsumeSchema anymore
Contributor
Author
|
@sijie I am closing this PR. I will send another patch with an alternative approach |
1 task
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
2 participants
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.
Motivation
When you develop a Source you can push KVRecords in order to send records with the KeyValue schema and set properly the KeySchema the ValueSchema and the Key encoding type.
On the Sink side you are receiving only Record, it is better to have a consistent behaviour
Modifications
Verifying this change
This change added tests