-
Notifications
You must be signed in to change notification settings - Fork 272
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
[PROPOSAL] Release standalone plugins, such as mapper-murmur3 #844
Comments
What other plugins aren't we shipping out of the box that live in https://github.com/opensearch-project/OpenSearch? Sounds like the right thing to do would be to extract those in their own repositories and put them on their own release schedule? @saratvemulapalli do you know more about this? |
I'm moving this to opensearch-build where we track release artifacts. |
Looks like the question here is to publish plugin artifacts for community contributed plugins. The first step is to publish maven artifacts for plugins in opensearch-project. |
[Triage] @bbarani can you look into this proposal and see how this could fit into our release process and schedule? |
We have already released native plugins to artifacts.opensearch.org as part of every release starting 1.2.0. You should be able to install it directly using the plugin install command. You can also install the standalone plugin by passing the path of the zip available within the manifest file of every distribution.
You can refer to this forum post for more details - https://discuss.opendistrocommunity.dev/t/download-urls-for-plugins-not-listed-anywhere/8297/5 We will work on uploading the zips to the artifacts.opensearch.org to support direct installation (without passing the URL) and you can track the status of that issue here #184 Feel free to re-open this issue if you still have any other questions. |
Actual
At the moment opensearch server plugin packages are published nowhere.
Expected
Opensearch plugins should be published on the website and/or on the github repository. I mean to publish not just compiled
jar
file, but azip
acceptable byopensearch-plugin
command line tool.Example
When I needed to use
mapper-murmur3
plugin, I was surprised that it is not shipped OOTB. After some googling I found a compiled binary of the plugin on maven - it was a jar file, but the command line tool rejected it. No info which format of the input is required, no info how thezip
package should looks like, no info what should be in theplugin-descriptor.properties
file inside this zip. Fortunately, I succeeded to build it and to install the plugin, but it is an extremely user-unfriendly way.Please, consider creating the proper CI workflow which will create these packages and publish them. Thank you.
The text was updated successfully, but these errors were encountered: