Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Allow extensions to contribute short names for new IndexManager implementations

Description

The only "third party" IndexManager we had so far is the InfinispanIndexManager - living in the Infinispan Query project - , which overrides the DefaultIndexManagerFactory as it actually also overrides the resolution of names.

This approach doesn't scale to other jars wanting to contribute additional short names, for example the Elasticsearch integration module can not define an additional IndexManagerFactory as that wouldn't "compose" with the Infinispan approach.

Rather than overriding a core service this needs an ad-hoc approach.

Activity

Show:

Yoann RodièreOctober 16, 2019 at 6:29 AM

There are ways to do this in Search 6 using the BeanConfigurer. We'll see if we need it when we upgrade Infinispan to Search 6.

Closing as out of date.

Sanne GrinoveroApril 18, 2016 at 7:18 PM

That code was in a branch containing the POC for the index-affinity implementation; turns out index affinity was ultimately merged without needing this.

Looks like we could go our own way: not allow overrides, but allow extensions as long as they don't contribute conflicting options (same name).

Gunnar MorlingApril 18, 2016 at 9:48 AM

, can you point me to ISPN's implementation of IndexManagerFactory? I could not find it with a quick search. Thanks!

Out of Date

Details

Assignee

Reporter

Components

Priority

Created February 24, 2016 at 9:31 PM
Updated October 16, 2019 at 6:29 AM
Resolved October 16, 2019 at 6:29 AM