Skip to content

Define earlyMessegeRejectPeriod as the period after the taskDuration#4990

Merged
nishantmonu51 merged 1 commit intoapache:masterfrom
elloooooo:feature-earlyMessageRejectPeriod-improve
Oct 26, 2017
Merged

Define earlyMessegeRejectPeriod as the period after the taskDuration#4990
nishantmonu51 merged 1 commit intoapache:masterfrom
elloooooo:feature-earlyMessageRejectPeriod-improve

Conversation

@elloooooo
Copy link
Copy Markdown
Contributor

The earlyMessageRejectPeriod was defined as the period after the kafkaIndexTask created.
If user set the taskDuration as PT6H and earlyMesssageRejectPeriod as PT1H, this kafkaIndexTask will throw away the data of last 5 hours. I don't think it's a good way to define the message window.
I think message window should like:
message window = lateMessageRejectPeriod + taskDuration + earlyMesssageRejectPeriod

So I make a little change to define earlyMessegeRejectPeriod as the period after the taskDuration.
And add a little debug log.

Copy link
Copy Markdown
Contributor

@gianm gianm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This style seems better. It's a behavior change, but the Kafka indexing service is experimental anyway, so I think it's ok to make changes like this without too much fanfare.

Will mark this "release notes" since the release notes should discuss the behavior change.

Copy link
Copy Markdown
Member

@nishantmonu51 nishantmonu51 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@nishantmonu51 nishantmonu51 merged commit 52a162e into apache:master Oct 26, 2017
@jon-wei jon-wei added this to the 0.12.0 milestone Jan 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants