damnMeddlingKid edited a comment on issue #10644: URL: https://github.com/apache/druid/issues/10644#issuecomment-840043076
> Why 0? If there are no matching rows, shouldn't the result be that no rows are returned, and not a value? We should consider all codepaths, You could be running this as a filtered aggregate along with other columns that do have values. It looks like in the case of default value replacement the aggregates are initialized with sentinel values that help the user distinguish "no result" because the plan can't return "null" in this case. I think the behaviour should be documented so that it doesn't come as a surprise to users. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org
