+1
2021년 3월 12일 (금) 오후 2:54, Jungtaek Lim 님이 작성:
> +1 (non-binding) Excellent description on SPIP doc! Thanks for the amazing
> effort!
>
> On Wed, Mar 10, 2021 at 3:19 AM Liang-Chi Hsieh wrote:
>
>>
>> +1 (non-binding).
>>
>> Thanks for the work!
>>
>>
>> Erik Krogen wrote
>> > +1 from me
+1 (non-binding) Excellent description on SPIP doc! Thanks for the amazing
effort!
On Wed, Mar 10, 2021 at 3:19 AM Liang-Chi Hsieh wrote:
>
> +1 (non-binding).
>
> Thanks for the work!
>
>
> Erik Krogen wrote
> > +1 from me (non-binding)
> >
> > On Tue, Mar 9, 2021 at 9:27 AM huaxin gao
>
> >
I agree with you to extend the documentation around this. Moreover I
support to have specific unit tests for this.
> There is clearly some demand for Spark to automatically clean up
checkpoints on shutdown
What about I suggested on the PR? To clean up the checkpoint directory at
shutdown one can
OK, perhaps the best course of action is to leave the current behavior
as-is but clarify the documentation for `.checkpoint()` and/or
`cleanCheckpoints`.
I personally find it confusing that `cleanCheckpoints` doesn't address
shutdown behavior, and the Stack Overflow links I shared
Thank you, Xiao, Wenchen and Hyukjin.
Bests,
Dongjoon.
On Thu, Mar 11, 2021 at 2:15 AM Hyukjin Kwon wrote:
> Just for an update, I will send a discussion email about my idea late this
> week or early next week.
>
> 2021년 3월 11일 (목) 오후 7:00, Wenchen Fan 님이 작성:
>
>> There are many projects
Just for an update, I will send a discussion email about my idea late this
week or early next week.
2021년 3월 11일 (목) 오후 7:00, Wenchen Fan 님이 작성:
> There are many projects going on right now, such as new DS v2 APIs, ANSI
> interval types, join improvement, disaggregated shuffle, etc. I don't
>
There are many projects going on right now, such as new DS v2 APIs, ANSI
interval types, join improvement, disaggregated shuffle, etc. I don't
think it's realistic to do the branch cut in April.
I'm +1 to release 3.2 around July, but it doesn't mean we have to cut the
branch 3 months earlier. We
