Skip to content

Conversation

@slinkydeveloper
Copy link
Member

This came out after the discussions in cloudevents/sdk-java#260

The problem with partition key extension is that it must be used in the right context and it should not be a default (or opt-out) behaviour, but it should be a very precise opt-in behaviour that only users "aware of the consequences" should adopt it.

Signed-off-by: Francesco Guardiani francescoguard@gmail.com

@slinkydeveloper
Copy link
Member Author

This PR also reformat the kafka spec with

prettier --write --prose-wrap=always kafka-protocol-binding.md 

@slinkydeveloper
Copy link
Member Author

@duglin It seems like travis is broken on a link of another page:

./community/open-source.md: Can't load url: https://vmware.github.io/dispatch/ (tried 5 times)

@duglin
Copy link
Collaborator

duglin commented Nov 19, 2020

@duglin It seems like travis is broken on a link of another page:

./community/open-source.md: Can't load url: https://vmware.github.io/dispatch/ (tried 5 times)

Yep - opened a PR to fix it.

topic, but the source is another transport (e.g. HTTP), and the user needs a way
to key the record. As a counter example, It doesn't make sense to use it when
the sink and source are Kafka topics, because this may cause the re-keying of
the records.
Copy link
Collaborator

@duglin duglin Nov 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to make it easier to find.... ^^^ is the real change

The 'key' of the Kafka message MAY be populated by a "Key Mapper" function,
which might map the key directly from one of the CloudEvent's attributes, but
might also use information from the application environment, from the
CloudEvent's data or other sources.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^^^ is real change

specific.

Every implementation SHOULD provide a default "Key Mapper" implementation that
Every implementation SHOULD provide an opt-in "Key Mapper" implementation that
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^^^ is real change

@duglin duglin closed this Dec 3, 2020
@duglin duglin deleted the branch cloudevents:master December 3, 2020 20:22
@duglin duglin reopened this Dec 3, 2020
@duglin
Copy link
Collaborator

duglin commented Jan 26, 2021

@clemensv I believe we're waiting for some suggested edits from you on this one, right?

@clemensv
Copy link
Contributor

There is a long backlogged AI for me to review this, but -- oddly -- I have no objections.

@duglin
Copy link
Collaborator

duglin commented Feb 25, 2021

ok - I'll add this to the agenda for today.
All - please give it one more look-over

@duglin
Copy link
Collaborator

duglin commented Feb 25, 2021

@slinkydeveloper there's a conflict - can you rebase?

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>
Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>
Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>
@duglin
Copy link
Collaborator

duglin commented Mar 2, 2021

This was approved during the 2/25 call - providing @slinkydeveloper rebased.
That's now done - and he fixed the RFC keyword issues.
@slinkydeveloper you ready for me to merge it?

@slinkydeveloper
Copy link
Member Author

@duglin feel free to push the merge button!

@duglin duglin merged commit 5eab4a2 into cloudevents:master Mar 3, 2021
jskeet pushed a commit to jskeet/spec that referenced this pull request Mar 30, 2021
* Relax a bit the partitioning extension

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>

* Mention streaming as a use case

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>

* Fix spec

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>
@slinkydeveloper slinkydeveloper deleted the kafka_clarification branch June 22, 2021 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants