Is your proposal related to a problem?

Extents save the original JSON responses in QFE together with some metadata. BUT all of that metadata really is part of the key. We could be much more efficient by avoid an intermediate marshaling/unmarshaling code (from & to protobuf).

The current code really only saves the original trace ID but, for example, it doesn't end up in the OTEL instrumentation and so on. And it's a really weird requirement in general - let's put this tidbit of information (whether some query was served from cache or no) into attributes instead of reusing same trace ID.

Describe the solution you'd like

Refactor extents handling to avoid intermediate json marshal/unmarshal step and just store (compressed) JSONs directly.

Describe alternatives you've considered

NA

Additional context

NA