PSeitz

@yollotltamayo https://github.com/quickwit-oss/tantivy/tree/main/src/query/range_query The code is sometimes bound to a fixed field in the schema. These would need to be replaced with something that can handle JSON, e.g. "myjson.fielda" https://github.com/quickwit-oss/tantivy/blob/main/src/query/range_query/range_query.rs#L335 A...

When the JSON field contains timestamps, we could support date aggregation queries on it, when the user could define the precision in the aggregation API. That would be a extension...

Related to https://github.com/quickwit-oss/tantivy/issues/1833

What does `+` mean here, did you mean `translations.fra:*`? I think * is not supported on a field value. It would make sense though.

You could test the `ExistsQuery` from that [PR](https://github.com/quickwit-oss/tantivy/pull/1834). May need some adjustment for JSON fields though

I implemented the `ValueBuilder` trait for `serde_json_borrow::Value`. In this bench it is slightly slower than the simd_json `serde` variant in most benches. I think it should slightly faster than `BorrowedValue`,...

> A sad bit is that we compare things twice: > > * the search_after part is acting as a first fence. > > * the head of the top...

Should be fixed with: https://github.com/quickwit-oss/quickwit/pull/4922

Another improvement would be to store aggregations of field caps in the cache instead per split one entry

Reopening, since wildcards are not yet supported e.g. `nested.*` `*.description`