[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-499) Pass a "filter" query to MassIndexing: index changed entity based on timestamp
[
https://hibernate.onjira.com/browse/HSEARCH-499?page=com.atlassian.jira.p...
]
Marc Schipperheyn commented on HSEARCH-499:
-------------------------------------------
I was thinking about this yesterday and what if in stead of a soft delete filter, you have
a soft delete @DocumentFieldBridge at the field level? Each bridge would determine if a
document gets removed, updated, deleted, based on the value of the field, just like the
filter does now. This way the MassIndexer could more easily access this information.
Downside would be a potential (slight?) performance loss with multiple bridges like this
in case of multi field evaluations.
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