[
https://hibernate.onjira.com/browse/HSEARCH-471?page=com.atlassian.jira.p...
]
Sanne Grinovero commented on HSEARCH-471:
-----------------------------------------
I would expect the actionInterceptor to be applied on subtypes, but am having no clean
idea on how to avoid demanding this repetition, unless we make the option mandatory or
split it to a different annotation.
I still remember that I was initially surprised that @Indexed was not inherited.
Could we add an option to have the "indexing feature" inherited, with the same
options?
Then you could have
{code}
@Indexed(inherited=true, actionInterceptor=NotIndexAction.class) //default to NOT index,
neither this type nor subtypes
@Indexed(inherited=false, actionInterceptor=DefaultIndexedAction.class) //current
behaviour, with both options at it's default{code}
What I don't like is that if I extend a type annotated with Indexed and change for
example the index name only, it would be confusing to guess which action is expected: the
inherited one or the one defined here? of course the default one, as annotations won't
allow us to understand if a value was defined explicitly or not.
Ability to selectively index an entity based on its state
---------------------------------------------------------
Key: HSEARCH-471
URL:
https://hibernate.onjira.com/browse/HSEARCH-471
Project: Hibernate Search
Issue Type: New Feature
Components: engine, mapping
Affects Versions: 3.1.1.GA
Reporter: Dobes Vandermeer
In our system we have entities that are searched but not all of them are available for
search - some of them are flagged as "removed". It would improve the efficiency
of our search subsystem if we could implement a kind of "filter" that blocked
these entities from being added to the search index, since we wouldn't have to make
that a search term and our indexes would be somewhat smaller.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira