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

Reworded the documentation for lastByKeyColumns. #1935

Conversation

jcferretti
Copy link
Member

Original discussion here:
#1825 (comment)

* aggregated.
* is {@code IGNORE}. If {@code lastByKeyColumns == true}, it is expected that {@code table} is an add-only
* stream, or the result of an aggregation; a general refreshing table where rows can change position in
* arbitrary ways (eg, the result of {@code sort}) is not allowed. In DH engine technical terms, when
Copy link
Member

Choose a reason for hiding this comment

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

e.g.

* is {@code IGNORE}. If {@code keySpec != null && !lastByKeyColumns}, it is expected that {@code table} will
* not produce any row shifts; that is, the publisher expects keyed tables to be streams, add-only, or
* aggregated.
* is {@code IGNORE}. If {@code lastByKeyColumns == true}, it is expected that {@code table} is an add-only
Copy link
Member

Choose a reason for hiding this comment

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

This is backwards. If {@code lastByKeyColumns == true} we will apply the aggregation ourselves, and so none of this wording applies.

* is {@code IGNORE}. If {@code lastByKeyColumns == true}, it is expected that {@code table} is an add-only
* stream, or the result of an aggregation; a general refreshing table where rows can change position in
* arbitrary ways (eg, the result of {@code sort}) is not allowed. In DH engine technical terms, when
* {@code lastByKeyColumns == true} the updates to {@code table} should not produce any row shifts. A table
Copy link
Member

Choose a reason for hiding this comment

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

There is a debate to be had about whether we actually want to restrict shifts for keyed tables. I remain convinced that the answer is yes. @cpwright should weigh in as well.

@jcferretti
Copy link
Member Author

I don't think I am adding any value here; this change is so small that is easily replicated as a new PR, and Charles and/or Ryan are in a much better position to decide what this javadoc should say, I add not value being in the middle of it.

@jcferretti jcferretti closed this Feb 8, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Feb 8, 2022
@jcferretti jcferretti deleted the cfs-kafkatools-lastbykeycolumns-doc-0 branch February 18, 2022 15:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants