-
Notifications
You must be signed in to change notification settings - Fork 86
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.
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
[compat] [controller] add rt topic name in store config #1293
Open
arjun4084346
wants to merge
6
commits into
linkedin:main
Choose a base branch
from
arjun4084346:rttopicname
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
arjun4084346
force-pushed
the
rttopicname
branch
3 times, most recently
from
November 14, 2024 00:57
6cedc00
to
20785a8
Compare
arjun4084346
changed the title
[controller] add rt topic name in store config
[compat] [controller] add rt topic name in store config
Nov 14, 2024
arjun4084346
force-pushed
the
rttopicname
branch
from
November 15, 2024 00:42
d195293
to
154b13a
Compare
lluwm
reviewed
Nov 15, 2024
...ent/src/test/java/com/linkedin/davinci/kafka/consumer/KafkaConsumerServiceDelegatorTest.java
Show resolved
Hide resolved
internal/venice-common/src/main/java/com/linkedin/venice/meta/Version.java
Outdated
Show resolved
Hide resolved
internal/venice-common/src/main/java/com/linkedin/venice/meta/VersionImpl.java
Outdated
Show resolved
Hide resolved
arjun4084346
changed the title
[compat] [controller] add rt topic name in store config
[DRAFT] [compat] [controller] add rt topic name in store config
Nov 15, 2024
arjun4084346
force-pushed
the
rttopicname
branch
from
November 15, 2024 22:15
9397239
to
f66c463
Compare
arjun4084346
changed the title
[DRAFT] [compat] [controller] add rt topic name in store config
[compat] [controller] add rt topic name in store config
Nov 18, 2024
arjun4084346
force-pushed
the
rttopicname
branch
from
November 20, 2024 16:52
e85ea7c
to
9c39313
Compare
fix serialization fix tests fix documentation move methods from Version to Utils
arjun4084346
force-pushed
the
rttopicname
branch
from
November 21, 2024 22:56
9c39313
to
59bb408
Compare
arjun4084346
changed the title
[compat] [controller] add rt topic name in store config
[DRAFT] [compat] [controller] add rt topic name in store config
Nov 22, 2024
arjun4084346
force-pushed
the
rttopicname
branch
from
November 22, 2024 04:23
11090e6
to
114803d
Compare
arjun4084346
force-pushed
the
rttopicname
branch
from
November 22, 2024 17:41
6ffddf4
to
5484ab5
Compare
arjun4084346
changed the title
[DRAFT] [compat] [controller] add rt topic name in store config
[compat] [controller] add rt topic name in store config
Nov 22, 2024
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.
Add a field
realTimeTopicName
in store and store-version hybrid configIn future, we want to provide users/admin ability to create a new real time topic, probably with some different configurations, e.g. partition count. This new real time topic would co-exist with the old real time topic for some time, so we want to give it a different name.
This PR will make all the components check the real time topic's name, if it exists, in Store/Store-Version hybrid config. If the config does not have any name, it would be assumed, that there is no new topic right now and we can use the old methodology "<store_name>_rt" to determine the real time topic name.
Verson.composeRealTimeTopic method is moved to Utils.
Utils.getRealTimeTopicName are the core methods of this PR.
When store is not hybrid, current version is also not hybrid, and two older versions are using two different rt topics.
This method will return one of those RT topic, because both the RT topics are "active" and will be having data mirroring tasks copying data to/from each other
Note that, in future, when creating new RT topic, I plan to add condition that there should not exists more than one rt topics, because it will increase data replication processes exponentially. So at one point, we will allow only two RT topics
Resolves #XXX
How was this PR tested?
added integration tests.
Does this PR introduce any user-facing changes?