reschke opened a new pull request, #3107:
URL: https://github.com/apache/jackrabbit-oak/pull/3107

   …ex (#3100)
   
   When FT_OAK-12249 and FT_OAK-12248 are both enabled, ElasticIndexWriter 
defers provisionIndex() from the constructor to the first updateDocument() or 
deleteDocuments() call. A reindex that produces zero documents never creates an 
Elasticsearch index or alias, eliminating the empty-index problem described in 
OAK-12249.
   
   Deployment order is enforced at runtime: isLazyProvisioningActive() returns 
true only when both toggles are on. Enabling FT_OAK-12249 alone logs a WARN and 
falls back to eager provisioning, preventing 404 errors on query paths that 
lack graceful 404 handling.
   
   ensureProvisioned() handles the incremental-write-after-empty-reindex case: 
if an alias does not exist when the first document arrives, it creates a new 
backing index with a fresh seed and points the alias at it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to