hanahmily opened a new issue, #13329: URL: https://github.com/apache/skywalking/issues/13329
### 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 Design a comprehensive schema to capture all essential tracing constructs (traces, spans, tags) while optimizing for storage efficiency and query performance. Key Features: - **Sparse Primary Index**: Implement a sparse index for the traceID primary key, with rows ordered by traceID to enable fast point queries and range scans. - **Query Column Files**: Store each queryable column (e.g., serviceName, operationName, status) in separate files. These files must support skipping indexes (min-max, bloom filter) to accelerate filtering. Rows in these files are ordered by `traceID-spanID` to maintain alignment with span data. - **Span Data File**: Store span data (e.g., start/end timestamps, tags, logs) in a dedicated file, ordered by `traceID-spanID`. This ordering ensures that spans from the same trace are grouped together for efficient retrieval. - **Merge Optimization**: For non-overlapping span files during merging (e.g., no overlapping `traceID-spanID` ranges), support direct concatenation without scanning file content to minimize merge time. ### 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: notifications-unsubscr...@skywalking.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
