You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2019. It is now read-only.
It would be nice if we moved marvel and any additional plugins to a configurable storage container. The only plugin required by this solution is the discovery plugin so we can make an exception and keep it in the solution. We don't want to be dictating what plugins should be used. We also don't want to make it difficult for people to add their own plugins for their purposes.
The text was updated successfully, but these errors were encountered:
I can have a look at this.
My proposal is to create a storage container holding x number of plugins. The worker role will download the plugins and copy them to the Elastc Search plugin folder upon initializing,
Yes, that is exactly what I was thinking. The only thing to keep in mind is the order of tasks. You can download everything at the same time but you must wait till elasticsearch is installed before you can extract the plugins to the plugin folder. The other option is see if elastic search supports multiple plugin folders. If that is the case then you can do everything concurrently.
tormodu
pushed a commit
to tormodu/Elasticsearch-Azure-PAAS
that referenced
this issue
Jan 7, 2015
It would be nice if we moved marvel and any additional plugins to a configurable storage container. The only plugin required by this solution is the discovery plugin so we can make an exception and keep it in the solution. We don't want to be dictating what plugins should be used. We also don't want to make it difficult for people to add their own plugins for their purposes.
The text was updated successfully, but these errors were encountered: