Search before asking
Description
This is a very special feature of ElasticSearch @wankai123 found from Zipkin using ElasticSearch to save spans.
In saving traces, tags are indexed as query conditions to make users easier to locate important traces, but meanwhile, the whole trace segment is already stored as binary(base64 encoded) in the no-indexing field. So most indexed tags are actually duplicated from the data table perspective.
I hope we could have a way to define a field/column of a table indexing(by different index types) but also not stored. All fields in this type are not allowed in projection clearly because they are stored, OAP could read those values from the binary field directly.
@wankai123 is going to propose this in ElasticSearch storage implementation.
Use case
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Search before asking
Description
This is a very special feature of ElasticSearch @wankai123 found from Zipkin using ElasticSearch to save spans.
In saving traces, tags are indexed as query conditions to make users easier to locate important traces, but meanwhile, the whole trace segment is already stored as binary(base64 encoded) in the no-indexing field. So most indexed tags are actually duplicated from the data table perspective.
I hope we could have a way to define a field/column of a table indexing(by different index types) but also not stored. All fields in this type are not allowed in
projectionclearly because they are stored, OAP could read those values from the binary field directly.@wankai123 is going to propose this in ElasticSearch storage implementation.
Use case
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct