[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-499?pag...
]
Marc Schipperheyn commented on HSEARCH-499:
-------------------------------------------
Right, but why not ask users to supply a DetachedCriteria or create the forClass part in
the API and let the user add createAliases and restrictions. Like a kind of intermediary
form, such as a MustJunction in HSearch. You can add the rowCount projection and id
projection yourself.
fts.createIndexer(clazz)
.restrictionsForClass(
MassIndexer.forClass()
.createAlias("validity","validity")
.add(Restrictions.le("validity.dteFrom", new Date())
.add(Restrictions.ge("validity.dteTo", new Date())
)
.purgeAllOnStart(true)
.optimizeOnFinish(true)
.threadsToLoadObjects(3)
.batchSizeToLoadObjects(30)
.threadsForSubsequentFetching(12)
.startAndWait();
Pass a "filter" query to MassIndexing: index changed entity
based on timestamp
------------------------------------------------------------------------------
Key: HSEARCH-499
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-499
Project: Hibernate Search
Issue Type: New Feature
Components: massindexer
Reporter: Emmanuel Bernard
Assignee: Sanne Grinovero
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