Hello Team, Lucene index is always asynchronous and the async index could lag behind by definition.
Sometimes we could have the same query better served by a property index, or traversing for example. In case the async index is lagging behind it could be that the traversing index is better suited to return the information as it will be more updated. As we know we run an async update every 5 seconds, we could come up with some algorithm to be used on the cost computing, that auto correct with some math the cost, increasing it the more the time passed since the last full execution of async index. WDYT? Davide
