syeerzy opened a new issue, #58204: URL: https://github.com/apache/doris/issues/58204
### 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 The aggregation table needs to support a First semantics (contrary to Replace aggregation, which retains the latest value, First only retains the first value) This will be a special aggregation type, because it has the specificity of "never updating", and it will become the only aggregation type that can be used for partitioning. ( Now all aggregation types cannot be used for partitioning) ### Use case Assuming that we have a batch of click event data in different games from kafka's boundless, we need to aggregate the clicks from the same user and the same game in the same game. The time of a game of different games may range from 10 seconds to hours. Because the data is boundless and may grow to infinity over time, the data volume of this aggregate table will also increase over time, and the table needs to be partitioned. In most cases, the event date is a good choice, but a game may take place at 23:59 and last until the next day. We can't predict that there may be other games with a longer game time in the future, so it's not easy to determine the time window to deal with it. Different games may have different rules. The way of expressing a game (self-increasing int, or uuid, etc.) is difficult to unify as the composition of partition rules. At present, it is impossible to solve this similar scenario (the business can't find a suitable key that can be used for partitioning, and only the aggregate column can be partitioned) And an aggregate type that never updates will solve this problem. ### 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]
