-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Remove SpawnModules #13034
Remove SpawnModules #13034
Conversation
The last use case of spawn modules was for plugins. This change handles plugin modules directly, and removes SpawnModules. closes elastic#12783
I synced up with master, and also removed PreProcessModule as it is no longer used. |
@@ -316,6 +333,11 @@ public synchronized IndexService createIndex(String sIndexName, @IndexSettings S | |||
modules.add(new IndexAliasesServiceModule()); | |||
modules.add(new IndexModule(indexSettings)); | |||
|
|||
for (Module pluginModule : pluginsService.indexModules(indexSettings)) { |
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 this actually used anywhere? I mean why would you add your own index modules? I really wonder if we need this kind of extension mechanism? I know it's unrelated but maybe we need a followup issue?
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 created #13059
LGTM |
@rjernst Did you mean to merge this in to 2.0 as well? |
Remove SpawnModules
back-ported to 2.0 branch as well |
The last use case of spawn modules was for plugins. This change handles
plugin modules directly, and removes SpawnModules.
closes #12783