-
Notifications
You must be signed in to change notification settings - Fork 59
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
Fail build on missing Javadocs #45
Conversation
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
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.
I scoped my comments to the documentation that was added
Signed-off-by: Daniel Widdis <[email protected]>
@@ -85,6 +93,12 @@ private DiscoveryNode getOpensearchNode() { | |||
return opensearchNode; | |||
} | |||
|
|||
/** | |||
* Handles a plugin request from OpenSearch. This is the first request for the transport communication and will initialize the extension and will be a part of OpenSearch bootstrap. |
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.
This is the first request
It would by very valuable to have the full lifecycle of this process documented, maybe here? Then additional parts of the process would link back to this comment with a @see
annotation
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.
Just to give some context here. During bootstrap OpenSearch will look for any extensions available running on a different port. Once discovered, read their extensions.yml file and get the metadata of that extension.
Thanks for iterating on this @dbwiddis, there is a lot of surface area here and its great to get a fine tooth comb looking over it and improvement maintainability of the codebase |
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Signed-off-by: Daniel Widdis <[email protected]>
Ready for review:
|
Signed-off-by: Daniel Widdis <[email protected]>
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.
This is a great start.
Thanks @dbwiddis !!
Signed-off-by: Daniel Widdis <[email protected]>
Added back the exclusion for netty4 and added the tracking issue. So now this should be mergeable. |
* @param settings The transport settings to configure. | ||
* @param threadPool A thread pool to use. | ||
* @return The configured Netty4Transport object. | ||
*/ | ||
public Netty4Transport getNetty4Transport(Settings settings, ThreadPool threadPool) { |
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.
For later: Can change this method to createNetty4Transport
.
Signed-off-by: Daniel Widdis <[email protected]>
Co-authored-by: Owais Kazi <[email protected]> Signed-off-by: Daniel Widdis <[email protected]>
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.
Not sure if part of this PR but we need OpenSearch license header for all the files
Signed-off-by: Daniel Widdis <[email protected]>
Make a new issue for this. There are license-check plugins. |
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.
Overall LGTM! Thanks @dbwiddis for all the changes
|
* Fail build on missing Javadocs Signed-off-by: Daniel Widdis <[email protected]> * Fix build errors from package rename Signed-off-by: Daniel Widdis <[email protected]> * Javadocs for ActionListener Signed-off-by: Daniel Widdis <[email protected]> * Javadocs for ExtensionsRunner Signed-off-by: Daniel Widdis <[email protected]> * Replace missing-javadoc and missing-doclet with require-javadoc Signed-off-by: Daniel Widdis <[email protected]> * Doc updates based on code review. Signed-off-by: Daniel Widdis <[email protected]> * Add javadocs for ResponseHandler classes Signed-off-by: Daniel Widdis <[email protected]> * Add javadocs to ExtensionSettings Signed-off-by: Daniel Widdis <[email protected]> * Disable javadocStrict check on netty4 package Signed-off-by: Daniel Widdis <[email protected]> * Reenable strict doc checks on netty4, fix errors Signed-off-by: Daniel Widdis <[email protected]> * Final tweaks Signed-off-by: Daniel Widdis <[email protected]> * Fix missing Netty4 params causing failure Signed-off-by: Daniel Widdis <[email protected]> * Don't use Werror, include strict check on private javadocs if present Signed-off-by: Daniel Widdis <[email protected]> * Exclude netty4 from checks and link to tracking issue Signed-off-by: Daniel Widdis <[email protected]> * Clarify and add links on future action for temporary exclusions Signed-off-by: Daniel Widdis <[email protected]> * Update comments per code review Co-authored-by: Owais Kazi <[email protected]> Signed-off-by: Daniel Widdis <[email protected]> * Update require-javadoc version, fix get/set typo Signed-off-by: Daniel Widdis <[email protected]> Co-authored-by: Owais Kazi <[email protected]>
Signed-off-by: Daniel Widdis [email protected]
Description
Javadocs:
Excluded Netty4 code as it is here temporarily; it will be eventually published to the central repository via OpenSearch, see opensearch-project/OpenSearch#3118
Issues Resolved
Fixes #27
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.