-
Notifications
You must be signed in to change notification settings - Fork 187
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
Conversation
docs/index.asciidoc
Outdated
|
||
* 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) |
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.
How about "The column whose value is to be tracked if use_column_value is set to true" ?
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.
Much better. Thanks for that. Changed.
@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). |
Logged #279 for phase 2 |
…e in record_last_run entry clickable. Reword description
LGTM |
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. Note that I didn't build the docs to test the asciidoc coding (assuming that you have done that).
Yes, I tested without issue |
karen.metts merged this into the following branches!
|
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