[
https://hibernate.onjira.com/browse/HSEARCH-499?page=com.atlassian.jira.p...
]
Sanne Grinovero commented on HSEARCH-499:
-----------------------------------------
Why at field level? What if I have multiple fields, and some request a delete and some
other request an update?
We could patch the MassIndexer to consider the soft delete logic, my problem is that
ideally I would need to translate the filters in SQL predicates so that I can restrict the
entities being loaded from the database.
Filtering the entities by having the user defined soft delete logic by "looking at
the entity state" is easy, but it would be much more efficient by loading only the
data we actually need.
Pass a "filter" query to MassIndexing: index changed entity
based on timestamp
------------------------------------------------------------------------------
Key: HSEARCH-499
URL:
https://hibernate.onjira.com/browse/HSEARCH-499
Project: Hibernate Search
Issue Type: New Feature
Components: massindexer
Reporter: Emmanuel Bernard
Assignee: Sanne Grinovero
Fix For: 4.1.0.Final
I was discussion the MassIndexer API. It would be nice to be able to filter the list of
Entity ids to reindex based on a query:
For example
select u.id from User u where u.lastUpdate >= :yesterday
or sue some kind of other flag.
This would be a nice useful trick.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira