[infinispan-issues] [JBoss JIRA] (ISPN-6430) Remote Queries do not allow per-entity index configurations
Adrian Nistor (JIRA)
issues at jboss.org
Thu Mar 24 10:48:00 EDT 2016
[ https://issues.jboss.org/browse/ISPN-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182017#comment-13182017 ]
Adrian Nistor commented on ISPN-6430:
-------------------------------------
I'm not against it but we should find a good reason to have it.
ATM all protobuf entities live in the same index and this spares us from the problems generated by creating indexes dynamically. We'll have to declare all indexed protobuf types at startup in the spirit of ISPN-6178 if we really want to split de indexes. I don't think that's nice for server mode.
> 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)
More information about the infinispan-issues
mailing list