Paul Masurel

The problem is the fact that the ingest queue has not been created right after create index has been called. It was observed in CI here: https://github.com/quickwit-oss/quickwit/actions/runs/5651558711/job/15309848879?pr=3677

We do not want to fix this issue until the work on the ingest api is done. In the meanwhile, I will add a workaround in the rest api tests.

@rdettai it is supposed to be fixed in `main` :( you are workign on main though I assume?

Tantivy went from -tantivy = { git = "https://github.com/quickwit-oss/tantivy/", rev = "6181c1e", default-features = false, features = [ +tantivy = { git = "https://github.com/quickwit-oss/tantivy/", rev = "92b5526", default-features = false,...

Not necessarily tantivy then

:) I didn't see that coming :D

@PSeitz This PR seems very safe BUT... it actually DOES something on the server side of ingest v1. It introduced a change (hopefully a bugfix) in the code of our...

@PSeitz can you take over this issue. You can ditch or use #5034 if you want. For the last part: 'term aggregations on all query', it would be nice to...

I could not tell if your text is describing the current state or not. For count all, we already have an optimization in main... but one thing to consider is...

This is low priority.