trinity-1686a

sstable block codec already has an 8bit field encoding whether a block is compressed, so it should be a matter of passing a bool to `DeltaWriter`, and modifying [this heuristic](https://github.com/quickwit-oss/tantivy/blob/9f81d59ecd283a4ce1b6527a447c705b5fba0b1a/sstable/src/delta.rs#L56)....

it looks like #4698. Is this with 0.8 (which doesn't have the corresponding fix) or with main/edge?

to be clear, that's an LNX issue, that relies on tantivy 0.18, right? the query parser was entirely rewritten over the last year and a half, with some newly added...

we may want to do the same with aggregations. I'm worried the Arc isn't all that useful. At the search-single-split level we end up modifying the AST systematically. This could...

it seems like this happens when a merge is running while the ingestion finishes. This sounds a lot like an issue we had with lambda deployments. Which brings the question,...

there is definitely a problem here. Last i checked, the retention policy is executed on a strict cron-like schedule. If many indexes share the same schedule frequency, they would all...

we also seem to execute all GC calls at once, but scoping them by index, which causes many consecutive call, and much more often (every 10 or so minutes). That's...

https://discord.gg/E5Hn54jNGP

i'm not actually sure we need this anyway, in the situation where this seemed useful, the field name actually gets remapped to something else entirely, and we don't go through...

before i review further, i have a major concern to express. for mostly historic reasons, start/end_timestamps are only precise up to the second, but the ast can express sub-second precision,...