In deep there is a limit on the way native search works. It will only search attribute/resource tags that are strings. This is the same as tempo. We can (I believe) fix this, but I assume this was done in tempo for a reason (maybe performance).
The open question is, do we need to support the complex types that tempo supports. Or do we just want these tags to be strings? at the moment a tab can be int, boolean, string, double, array, bytes, map. This makes it quite complex to render and search.
I cannot see a reason why these tags would be anything but strings.
In deep there is a limit on the way native search works. It will only search attribute/resource tags that are strings. This is the same as tempo. We can (I believe) fix this, but I assume this was done in tempo for a reason (maybe performance).
The open question is, do we need to support the complex types that tempo supports. Or do we just want these tags to be strings? at the moment a tab can be int, boolean, string, double, array, bytes, map. This makes it quite complex to render and search.
I cannot see a reason why these tags would be anything but strings.