zyp-V opened a new issue, #64244: URL: https://github.com/apache/doris/issues/64244
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Description In point query scenarios, users need to enable store_row_column, which stores data in columnar format and additionally combines all columnar data into a single large JSON field for separate storage, resulting in severe storage bloat. Therefore, the Row-Store Only solution is introduced for scenarios dominated by point queries with lightweight analytics. Its core goal is to drastically reduce physical storage footprint by retaining only the primary key index and a complete row store column (DORIS_ROW_STORE_COL), while keeping the point query performance of the UNIQUE KEY model largely unchanged. ### Use case CREATE TABLE `tbl_point_query` ( `k` int(11) NULL, `v1` decimal(27, 9) NULL, `v2` varchar(30) NULL, `v3` varchar(30) NULL, `v4` date NULL, `v5` datetime NULL, `v6` float NULL, `v7` datev2 NULL ) ENGINE=OLAP UNIQUE KEY(`k`) COMMENT 'OLAP' DISTRIBUTED BY HASH(`k`) BUCKETS 1 PROPERTIES ( "enable_unique_key_merge_on_write" = "true", "store_row_column" = "true", "row_store_only" = "true"); ### Related issues _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
