hanahmily opened a new issue, #12877:
URL: https://github.com/apache/skywalking/issues/12877

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no 
similar feature requirement.
   
   
   ### Description
   
   
   ### Current Behavior
   
   In BanyanDB's `Measure` index mode, the **measure name** and **tags** 
associated with an **Entity** are currently encoded within the `_id` field. 
This approach optimizes storage space by consolidating key identifying 
information into a single field.
   
   ### Issue
   
   While encoding the measure name and tags into the `_id` field benefits 
storage efficiency, it introduces significant drawbacks in search performance:
   
   - **Increased Search Latency:** Queries that need to filter or search based 
on measure names or specific tags must parse the `_id` field, leading to longer 
query times.
   - **Reduced Flexibility:** Combining multiple attributes into a single field 
limits the ability to perform more complex queries and aggregations on 
individual characteristics.
   
   ### Proposed Enhancement
   
   To address these issues, I propose **decoupling the measure name and tags 
from the `_id` field** by introducing separate fields for each. This structural 
change aims to enhance search performance and provide greater flexibility in 
querying.
   
   **Proposed Changes:**
      - Introduce a dedicated field for the **measure name**.
      - Introduce separate fields for each **tag** associated with the Entity.
   
   
   ### Use case
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a pull request to implement this on your own?
   
   - [ ] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to