Skip to content
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

Enable Prospector to Update state without Harvester #1978

Merged
merged 1 commit into from
Jul 8, 2016

Conversation

ruflin
Copy link
Contributor

@ruflin ruflin commented Jul 6, 2016

Until now it was always necessary to create a harvester to update the state. This now allows the prospector to update a state for example on detection of a file that was renamed but no updates area available, so no harvester has to be started.

Changes:

  • Rename FileState to State in harvester
  • Remove lastScan time as not needed anymore.
  • Cleanup state, enabled prospector to update state directly
  • Make sendUpdateState private
  • Make state private in harvester
  • Remove mutex as not needed anymore
  • Rename spoolerChan to prospectorChan as events are sent to prospector first
  • Make path variable private

Until now it was always necessary to create a harvester to update the state. This now allows the prospector to update a state for example on detection of a file that was renamed but no updates area available, so no harvester has to be started.

Changes:
* Rename FileState to State in harvester
* Remove lastScan time as not needed anymore.
* Cleanup state, enabled prospector to update state directly
* Make sendUpdateState private
* Make state private in harvester
* Remove mutex as not needed anymore
* Rename spoolerChan to prospectorChan as events are sent to prospector first
* Make path variable private
@tsg tsg merged commit f9754a6 into elastic:master Jul 8, 2016
@ruflin ruflin mentioned this pull request Jul 18, 2016
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants