On 18/08/2024 23:37, Benoit TELLIER wrote:
Should we trigger an automatic re-index?
Got the point, this could be a good idea but:
- this would be a lucene specific feature IMO
- starting a heavy task on admin behalf can lead to unwanted heavy duty jobs
running - without indication on volumetry, expected indxing time etc sizing
the paralelism of the reindexing would be tricky - One might live without
index... (especially on top of implementations allowing search overrides).
Hmm... in case of "One might live without index." I think it's not so important... and after our
recent migration I don't think it's so relevant (to us) :)
should we finish the operation with the explicit "commit" operation?
+1
We could add a `postReindexing()` method for search indexes which commits for
Lucene and noop for Opensearch + scanning.
Then calling it in reindexing task would be a no brainer.
Do you think you can contribute this?--
Best regards,
Benoit TELLIER
Hope it's ok: https://github.com/apache/james-project/pull/2381
wk.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
