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

Clarify use of use_column_value #277

Closed
wants to merge 1 commit into from

Conversation

karenzone
Copy link
Contributor

@karenzone karenzone commented Mar 29, 2018

Clarify use of use_column_value.
Make last_run_metadata_path reference in record_last_run entry clickable.

Phase 1 fix for #273.
Phase 2 will involve reworking the topic

@karenzone karenzone changed the title Clarify use of use_column_value. Clarify use of use_column_value Mar 29, 2018
@karenzone karenzone added the docs label Mar 29, 2018

* Value type is <<string,string>>
* There is no default value for this setting.

If tracking column value rather than timestamp, the column whose value is to be tracked
The column whose value is to be tracked (if tracking column value rather than the last time the query was run)
Copy link
Contributor

Choose a reason for hiding this comment

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

How about "The column whose value is to be tracked if use_column_value is set to true" ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Much better. Thanks for that. Changed.

@jakelandis
Copy link
Contributor

@karenzone - changes look good. one minor suggestion.

For phase 2, I will log a proposal issue. I think we can get rid of one (maybe two of these settings).

@jakelandis
Copy link
Contributor

Logged #279 for phase 2

…e in record_last_run entry clickable.

Reword description
@jakelandis
Copy link
Contributor

LGTM

Copy link

@dedemorton dedemorton left a comment

Choose a reason for hiding this comment

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

LGTM. Note that I didn't build the docs to test the asciidoc coding (assuming that you have done that).

@karenzone
Copy link
Contributor Author

Yes, I tested without issue

@elasticsearch-bot
Copy link

karen.metts merged this into the following branches!

Branch Commits
master 8a0f7de

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.

4 participants