[GitHub] [doris] jlerebours commented on issue #17309: [Bug] Materialized view error: Aggregation type must be the same as base column

["jlerebours (via GitHub)" <gi...@apache.org>]

jlerebours commented on issue #17309:
URL: https://github.com/apache/doris/issues/17309#issuecomment-1463462695

   Just giving some more information, after investigating a bit more : 
   The problem is actually about the aggregation type and not as I said the data type (int, varchar, etc)
   
   And more particularly one thing that I don't get is that we have to keep the same type as original/base column meaning that i have to use : 
   - min(k1) in materialized view if k1 is MIN 
   - max(k2) in materialized view if k2 is MAX 
   - sum(k3) in materialized view if k3 is SUM
   - but what about REPLACE type ? that is my actual problem
   
   And this leads to my question : why can't we do some sum(k1) if k1 is MIN ?
   The main purpose of views and aggregating is often to sum stuff even if model is MIN.
   
   But my main question is : how to handle columns that are of type REPLACE ?


-- 
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: commits-unsubscribe@doris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org