-
Notifications
You must be signed in to change notification settings - Fork 63
Fixing a issue where feedoptions are getting overridden #312
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
Conversation
…y they are being initialized.
moderakh
left a comment
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
kushagraThapar
left a comment
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!
David-Noble-at-work
left a comment
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
moderakh
left a comment
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
Doc producers are spun for each partition range, and each one should have its own copy of feedoptions. In the existing implementation same copy of feedoptions is being used for all the producers due to which there is a possibility of loosing continuation token depending on the order of creation of document producers when multiple (>2) partition ranges are present. This PR addresses this issue and ensures feedoptions are set properly for each producer.