d and what do the other sql engines do in this case.
Tom
On Monday, January 20, 2020, 12:07:54 AM CST, Dongjoon Hyun
wrote:
Hi, All.
According to our policy, "Correctness and data loss issues should be considered
Blockers".
- http://spark.apache.org/contributing.html
Sin
ut and I'm not an
>> expert on SQL standard and what do the other sql engines do in this case.
>>
>> Tom
>>
>> On Monday, January 20, 2020, 12:07:54 AM CST, Dongjoon Hyun <
>> dongjoon.h...@gmail.com> wrote:
>>
>>
>> Hi, All.
>>
dongjoon.h...@gmail.com> wrote:
>
>
> Hi, All.
>
> According to our policy, "Correctness and data loss issues should be
> considered Blockers".
>
> - http://spark.apache.org/contributing.html
>
> Since we are close to branch-3.0 cut,
> I want to ask
L
standard and what do the other sql engines do in this case.
Tom
On Monday, January 20, 2020, 12:07:54 AM CST, Dongjoon Hyun
wrote:
Hi, All.
According to our policy, "Correctness and data loss issues should be considered
Blockers".
- http://spark.apache.org/contribut
://issues.apache.org/jira/browse/SPARK-28344
>
> On Mon, Jan 20, 2020 at 2:07 PM Dongjoon Hyun
> wrote:
>
>> Hi, All.
>>
>> According to our policy, "Correctness and data loss issues should be
>> considered Blockers".
>>
>> - http://
ur policy, "Correctness and data loss issues should be
> considered Blockers".
>
> - http://spark.apache.org/contributing.html
>
> Since we are close to branch-3.0 cut,
> I want to ask your opinions on the following correctness and data loss
> issues.
>
> SPA
Hi, All.
According to our policy, "Correctness and data loss issues should be
considered Blockers".
- http://spark.apache.org/contributing.html
Since we are close to branch-3.0 cut,
I want to ask your opinions on the following correctness and data loss
issues.
SPARK-30218 Co
