Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PIP-43: Producer Send Message with Different Schema #5141

Closed
3 tasks done
yittg opened this issue Sep 6, 2019 · 5 comments
Closed
3 tasks done

PIP-43: Producer Send Message with Different Schema #5141

yittg opened this issue Sep 6, 2019 · 5 comments
Assignees
@yittg
Labels
area/client type/feature The PR added a new feature or issue requested a new feature
Milestone
2.5.0

Comments

@yittg
Copy link
Contributor

yittg commented Sep 6, 2019 •
edited
Loading

This is a master issue for tracking the work to implement PIP-43.

  • core implementation.
  • expose newMessage to interface with different parameterized type.
  • move general SchemaHash to pulsar-common module.
@yittg yittg added the type/feature The PR added a new feature or issue requested a new feature label Sep 6, 2019
@yittg
Copy link
Contributor Author

yittg commented Sep 6, 2019 •
edited
Loading

cc @sijie. BTW, would you help to update the PIP wiki, some typos fixed and header supplemented, check out here.

@sijie
Copy link
Member

sijie commented Sep 6, 2019

@yittg done

@yittg yittg mentioned this issue Sep 10, 2019
Merged
1 task
sijie pushed a commit that referenced this issue Oct 25, 2019
@yittg @sijie
[PIP-43] Support producer to send msg with different schema (#5165)
13e35f7 
Master Issue: #5141 

### Motivation

Implement part-1 of [PIP-43](https://github.com/apache/pulsar/wiki/PIP-43%3A-producer-send-message-with-different-schema#changespart-1).

### Modifications

* New message api to specify message schema explicitly;
* Mechanism of registering schema on producing;
* Batch message container support to check message schema;
* Configuration for seamless introduction of this feature;
This was referenced Oct 25, 2019
Merged
Merged
sijie pushed a commit that referenced this issue Nov 5, 2019
@yittg @sijie
expose new message with different schema (#5517)
669b916 
Master Issue: #5141 

Expose new message with different schema interface, which not required same parameterized type with the producer.
Since the producer and messages sent by it may have different inner types, it's better to have a type agnostic producer interceptor with a checkin method.
@yittg
Copy link
Contributor Author

yittg commented Nov 6, 2019

@sijie, PIP-43 has been fully implemented, may we close this issue?

@sijie sijie added this to the 2.5.0 milestone Nov 6, 2019
@sijie
Copy link
Member

sijie commented Nov 6, 2019

@yittg yes. closing it now and will update the status of the PIP.

@sijie sijie closed this as completed Nov 6, 2019
@sijie
Copy link
Member

sijie commented Nov 6, 2019

@yittg well done!

@yittg yittg mentioned this issue Nov 6, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yittg yittg

Labels
area/client type/feature The PR added a new feature or issue requested a new feature
Projects
None yet
Milestone
2.5.0
Development

No branches or pull requests
2 participants
@sijie @yittg