Initial take at supporting topics in messaging #4956
Closed
Conversation
This file contains 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
derekperkins
force-pushed
the
message-topics
branch
from
df6289e
to
cb74f57
Compare
Signed-off-by: Derek Perkins <derek@derekperkins.com>
Signed-off-by: Derek Perkins <derek@derekperkins.com>
derekperkins
force-pushed
the
message-topics
branch
from
cb74f57
to
7fc5551
Compare
Signed-off-by: Derek Perkins <derek@derekperkins.com>
|
closing in favor of #5011 |
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.
This isn't functional, but should describe well enough the approach I am suggesting. With minimal changes to the existing flow, it stores a map of topics on the engine. Then on inserts, it checks to see if the table name references a topic. If so, it recursively replaces the insert statement table with each of the subscribed message table names. Topics are insert only. Updates and deletes only happen on the individual message tables.
Fixes #4940