[infinispan-issues] [JBoss JIRA] (ISPN-6430) Remote Queries do not allow per-entity index configurations

[Gustavo Fernandes (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185801#comment-13185801 ] 

Gustavo Fernandes commented on ISPN-6430:
-----------------------------------------

bq.  I'm not against it but we should find a good reason to have it.

One reason would be symmetry: library mode config when transposed to server behaves differently at the moment (see forum reference).
Other reason would be performance. What if one indexed cache has only a handful of entries and other index cache millions? 

bq. and this spares us from the problems generated by creating indexes dynamically. We'll have to declare all indexed protobuf types at startup

Right, that would be necessary if one wishes to control config on a per index basis. Hibernate Search by default names indexes using the class name of the entity, I'm wondering if it'd be possible to do something similar when indexing protobuf entities, i.e., take the type name and pass it to hibernate search.

> Remote Queries do not allow per-entity index configurations
> -----------------------------------------------------------
>
>                 Key: ISPN-6430
>                 URL: https://issues.jboss.org/browse/ISPN-6430
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Remote Querying
>            Reporter: Gustavo Fernandes
>
> When using Infinispan in library mode, it's possible to define a per-entity index configuration, so this is possible:
> {code:java}
> cacheCfg.indexing().index(Index.ALL)
> .addIndexedEntity(Car.class)
> .addIndexedEntity(Person.class)
> .addProperty("hibernate.search.person.directory_provider", "ram")
> .addProperty("hibernate.search.car.indexmanager","org.infinispan.query.indexmanager.InfinispanIndexManager")
> {code}
> Different entities can live in different indexes, with a complete different storage and index manager.
> Since when using remote queries there is a synthetic entity being created, this capability is lost.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)