-
Notifications
You must be signed in to change notification settings - Fork 14k
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
KAFKA-5274: AdminClient Javadoc improvements #3316
Conversation
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
38ba7be
to
5f1e1c9
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
public Map<ConfigResource, KafkaFuture<Void>> results() { | ||
return futures; | ||
} | ||
|
||
/** | ||
* Return a future which succeeds only if all the alter configs succeed. |
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.
Perhaps add "operation"? So "only if all the alter configs operations succeed." ?
/** | ||
* Return whether the config value is sensitive. The value is always set to null by the broker if the config value | ||
* is sensitive. | ||
*/ | ||
public boolean isSensitive() { |
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.
Is it more kafka-like to name this 'sensitive' instead of isSensitive?
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.
Kafka drops getters, but booleans are a little difference in that they can be pretty unclear without a prefix. I noticed this and a few other inconsistencies, but wanted to keep this PR purely as Javadoc changes.
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.
ok
public boolean isSensitive() { | ||
return isSensitive; | ||
} | ||
|
||
/** | ||
* Return whether the config is read-only and cannot be updated. | ||
*/ | ||
public boolean isReadOnly() { |
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.
readOnly instead of isReadOnly?
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.
Same as my other comment about limiting this PR to Javadoc changes.
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.
ok
public boolean internal() { | ||
return internal; | ||
} | ||
|
||
/** | ||
* A map from partition id to its leadership and replica information. |
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 "* A map from partition id to the leadership and replica information for that partition"
public AccessControlEntry(String principal, String host, AclOperation operation, AclPermissionType permissionType) { | ||
Objects.requireNonNull(principal); | ||
Objects.requireNonNull(host); | ||
Objects.requireNonNull(operation); | ||
assert operation != AclOperation.ANY; | ||
assert(operation != AclOperation.ANY); | ||
Objects.requireNonNull(permissionType); | ||
assert permissionType != AclPermissionType.ANY; |
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.
Should change this one as well if you are going to change the assert above to have parentheses
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.
That was accidental, I have fixed it locally, but didn't push it yet.
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.
Looks good overall. Does it make sense to do the ExtendedDeserializer, ExtendedSerializer, Serializer in this patch, or should we have another one fo that, since they're not really related to adminclient...? [edit: oh, I see you have that in the PR description... never mind]
@cmccabe, I can do a separate PR for the Serializer changes, if you prefer. |
The adminclient parts LGTM. I do have a preference to doing the serializer changes in a separate PR, although I don't feel strongly about it. |
9ad4edb
to
e3df61c
Compare
Moved serializer javadoc changes to a separate PR as requested: #3330 |
@gwenshap or @rajinisivaram, maybe one of you can review and merge this javadoc PR. @cmccabe has reviewed it. |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
It includes InterfaceStability annotation.
e3df61c
to
ac06459
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Test failure is unrelated. |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
ebc623b
to
1a65c10
Compare
Refer to this link for build results (access rights to CI server needed): |
LGTM. Really nice work, @ijuma. |
Publish Javadoc for common.annotation package, which contains InterfaceStability. Finally, mark AdminClient classes with `Evolving` instead of `Unstable`. Author: Ismael Juma <ismael@juma.me.uk> Reviewers: Colin Mccabe, Gwen Shapira Closes #3316 from ijuma/kafka-5274-admin-client-javadoc (cherry picked from commit b20d933) Signed-off-by: Gwen Shapira <cshapi@gmail.com>
Refer to this link for build results (access rights to CI server needed): |
Publish Javadoc for common.annotation package, which contains
InterfaceStability.
Finally, mark AdminClient classes with
Evolving
instead ofUnstable
.