Thanks, Tom.
I agree that emails are good for urgent announcement and reaching fast
agreement. Also, more visible in a short time period.
However, some correctness issues are long-standing and sometime they
changes their faces with different JIRA IDs. We can see the relationship
easily in the JIR
I was just thinking an info email (perhaps tagged with correctness/dataloss)
to dev rather than an official vote, that way its more visible and if anyone
sees it and disagrees with the targeting it can be discussed on that thread.
It might also just bring more visibility to those important is
Hi, All.
Currently, there is only one correctness issue which is targeting at 2.4.5.
SPARK-28344 Fail the query if detect ambiguous self join
-> Duplicated by
SPARK-10892 Join with Data Frame returns wrong results
SPARK-27547 fix DataFrame self-join problems
SPA
Yes. That is what I pointed in `Unfortunately, we didn't build a consensus
on what is really blocked by that.` If you are suggesting a vote, do you
mean a majority-win vote or an unanimous decision? Will it be a permanent
decision?
> I think the other interesting thing here is how exactly to come
thanks for bringing this up.
A) I'm not clear on this one as to why affected and target would be different
initially, other then the reasons target versions != fixed versions. Is the
intention here just to say, if its already been discussed and came to consensus
not needed in certain release?
