LakshSingla commented on issue #16331: URL: https://github.com/apache/druid/issues/16331#issuecomment-2247450573
> The stringMin/stringMax aggregation should return a string which can be filtered on without finalization, unlike a complex aggregation like stringFirst/StringLast. It should be usable at ingest and at query time. Eventually, the aggregator could include a configuration property for the collation to be used for the comparison. What's the use case of such an aggregation? Intermediate results are important for merging along the way, so I am unsure if I am interpreting the ask correctly. Can you share the pain point you are facing with the way Druid is right now? That would help me understand it better. > directly consumed without finalization At this point, intermediate results/finalization is a necessary evil - we require it to merge the intermediate results, and finalizing makes sure that the users have as little knowledge about it. > without special serializing/deserializing What does this mean? > and without writing custom logic (eg, extensions) What is meant by a "custom logic"? -- 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-unsubscr...@druid.apache.org 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
