Re: Combining multiple aggregations with annotate()

Hi Simon, In addition to what's documented, that's another way annotate() gives the wrong result. There are a lot of duplicates of #10060, and there are a lot of people who run into this issue. Given the age of the ticket and the lack of a simple backward compatible solution, what would be t

Re: Combining multiple aggregations with annotate()

While addressing the issue is complex and will require quite a bit of work to solve in a backward-compatible way I believe that it should be feasible to emit a MultipleMultiValuedJoin(RuntimeWarning) with pointers for alternatives (e.g. using subqueries) without too much hassle when aggregation

Re: Combining multiple aggregations with annotate()

In that case, at least there should be a warning message in the documentation. And what do you think of the example? Isn't it contradicting the documentation? On Wednesday, January 5, 2022 at 5:16:43 PM UTC+3 niccol...@gmail.com wrote: > I would be in favor of a real time information about the

Re: Combining multiple aggregations with annotate()

I haven’t looked at the current warning in a while but I do remember thinking that it could be more prominent. Kye > On 5 Jan 2022, at 10:16 pm, Niccolò Mineo wrote: > > I would be in favor of a real time information about the issue. > Il giorno mercoledì 5 gennaio 2022 alle 15:13:17 UTC+1 Y

Re: Combining multiple aggregations with annotate()

I would be in favor of a real time information about the issue. Il giorno mercoledì 5 gennaio 2022 alle 15:13:17 UTC+1 Yonas ha scritto: > Hello, > > There's a ticket opened 13 > years ago explaining a problem with combining multiple aggregations with