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

Add type to state info #4185

Merged
merged 1 commit into from
May 3, 2017
Merged

Add type to state info #4185

merged 1 commit into from
May 3, 2017

Conversation

ruflin
Copy link
Contributor

@ruflin ruflin commented May 3, 2017

With the introduction of new prospector types each prospector can have different state information. To differentiate between the different states for the prospector the type was added to each registry state.

With the introduction of new prospector types each prospector can have different state information. To differentiate between the different states for the prospector the `type` was added to each registry state.
Timestamp time.Time `json:"timestamp"`
TTL time.Duration `json:"ttl"`
Type string `json:"type"`
Copy link
Contributor

Choose a reason for hiding this comment

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

Name it "input_type" to differentiate it from the "document_type"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm hoping to have only one type in the future. More accurate here would be ProspectorType but as I try to keep the state as "independent" as possible with potentially have it in libbeat one day, I would just call it Type.

@tsg tsg merged commit 5e02b0b into elastic:master May 3, 2017
@ruflin ruflin deleted the state-type branch May 10, 2017 10:29
@ruflin ruflin mentioned this pull request May 10, 2017
14 tasks
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.

2 participants