HI.. is there any future roadmap to have inverted index for logs table , seems existing tokenby_v1 is taking time to search for a string in body column. Elapsed: 176.632 sec, read 1.67 billion rows, 3.87 TB (INDEX body_idx body TYPE tokenbf_v1(10240, 3, 0) GRANULARITY 4)

The last time we tested the inverted index, it didn't bring any significant change, but it has been quite some time since then, and I think we should reevaluate this.