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

KAFKA-5274: AdminClient Javadoc improvements #3316

Closed
wants to merge 10 commits into from

Conversation

ijuma
Copy link
Contributor

@ijuma ijuma commented Jun 13, 2017

Publish Javadoc for common.annotation package, which contains
InterfaceStability.

Finally, mark AdminClient classes with Evolving instead of Unstable.

@asfbot
Copy link

asfbot commented Jun 13, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5214/
Test FAILed (JDK 8 and Scala 2.12).

@asfbot
Copy link

asfbot commented Jun 13, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5230/
Test FAILed (JDK 7 and Scala 2.11).

@ijuma ijuma force-pushed the kafka-5274-admin-client-javadoc branch from 38ba7be to 5f1e1c9 Compare June 13, 2017 16:27
@asfbot
Copy link

asfbot commented Jun 13, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5216/
Test FAILed (JDK 8 and Scala 2.12).

@asfbot
Copy link

asfbot commented Jun 13, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5232/
Test FAILed (JDK 7 and Scala 2.11).

public Map<ConfigResource, KafkaFuture<Void>> results() {
return futures;
}

/**
* Return a future which succeeds only if all the alter configs succeed.
Copy link
Contributor

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() {
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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() {
Copy link
Contributor

Choose a reason for hiding this comment

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

readOnly instead of isReadOnly?

Copy link
Contributor Author

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.

Copy link
Contributor

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.
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 "* 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;
Copy link
Contributor

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

Copy link
Contributor Author

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.

Copy link
Contributor

@cmccabe cmccabe left a 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]

@ijuma
Copy link
Contributor Author

ijuma commented Jun 13, 2017

@cmccabe, I can do a separate PR for the Serializer changes, if you prefer.

@ijuma ijuma changed the title [WIP] KAFKA-5274: AdminClient Javadoc improvements KAFKA-5274: AdminClient Javadoc improvements Jun 14, 2017
@cmccabe
Copy link
Contributor

cmccabe commented Jun 14, 2017

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.

@ijuma ijuma force-pushed the kafka-5274-admin-client-javadoc branch from 9ad4edb to e3df61c Compare June 14, 2017 01:29
@ijuma
Copy link
Contributor Author

ijuma commented Jun 14, 2017

Moved serializer javadoc changes to a separate PR as requested: #3330

@ijuma
Copy link
Contributor Author

ijuma commented Jun 14, 2017

@gwenshap or @rajinisivaram, maybe one of you can review and merge this javadoc PR. @cmccabe has reviewed it.

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5277/
Test PASSed (JDK 7 and Scala 2.11).

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5261/
Test PASSed (JDK 8 and Scala 2.12).

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5282/
Test PASSed (JDK 7 and Scala 2.11).

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5266/
Test PASSed (JDK 8 and Scala 2.12).

@ijuma ijuma force-pushed the kafka-5274-admin-client-javadoc branch from e3df61c to ac06459 Compare June 14, 2017 12:00
@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5295/
Test FAILed (JDK 7 and Scala 2.11).

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5279/
Test PASSed (JDK 8 and Scala 2.12).

@ijuma
Copy link
Contributor Author

ijuma commented Jun 14, 2017

Test failure is unrelated.

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5283/
Test FAILed (JDK 8 and Scala 2.12).

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5299/
Test FAILed (JDK 7 and Scala 2.11).

@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5300/
Test PASSed (JDK 7 and Scala 2.11).

@gwenshap
Copy link
Contributor

LGTM. Really nice work, @ijuma.

asfgit pushed a commit that referenced this pull request Jun 14, 2017
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>
@asfgit asfgit closed this in b20d933 Jun 14, 2017
@asfbot
Copy link

asfbot commented Jun 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5284/
Test PASSed (JDK 8 and Scala 2.12).

@ijuma ijuma deleted the kafka-5274-admin-client-javadoc branch June 18, 2017 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants