-
Notifications
You must be signed in to change notification settings - Fork 51
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
Make max.pending.records
property reloadable
#207
Make max.pending.records
property reloadable
#207
Conversation
9cff79b
to
a8f71f2
Compare
a8f71f2
to
90c51e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for delaying the review.
Thanks! Left a comment but overall looks good.
Also could you add an integration test in PropertyReloadRequestTest
to check dynamic max.pending.records reload works?
processor/src/main/java/com/linecorp/decaton/processor/runtime/internal/PartitionContexts.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Left only nits comment
processor/src/it/java/com/linecorp/decaton/processor/PropertyReloadRequestTest.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
This PR updates
PartitionContexts
so themax.pending.records
property can be reloaded at runtime, similar to thepartition.concurrency
property.Modifications:
PartitionContexts
and register it forCONFIG_MAX_PENDING_RECORDS
PartitionContext
now reads the property value fromPartitionScope
ProcessorProperties
Javadoc formattingunchecked
code in tests