I'd like to volunteer as the release manager for the next Spark 3.0 preview.
On Mon, Dec 9, 2019 at 2:34 PM Reynold Xin wrote:
> If the cost is low, why don't we just do monthly previews until we code
> freeze? If it is high, maybe we should discuss and do it when there are
> people that volunte
If the cost is low, why don't we just do monthly previews until we code freeze?
If it is high, maybe we should discuss and do it when there are people that
volunteer
On Sun, Dec 08, 2019 at 10:32 PM, Xiao Li < gatorsm...@gmail.com > wrote:
>
>
>
> I got many great feedbacks from the com
I got many great feedbacks from the community about the recent 3.0
preview release. Since the last 3.0 preview release, we already have 353
commits [https://github.com/apache/spark/compare/v3.0.0-preview...master].
There are various important features and behavior changes we want the
community to t
Hm, so they look pretty similar except for minor differences in the
actual script run. Is there any reason this should be different? Would
it be reasonable to try making the 'new' one work like the 'old' one
if the former isn't working?
But I still can't figure out why it causes the same odd error
Hi everyone,
I have a conflict with the normal DSv2 sync time this Wednesday and I'd
like to attend to talk about the TableProvider API.
Would it work for everyone to have the sync at 6PM PST on Tuesday, 10
December instead? I could also make it at the normal time on Thursday.
Thanks,
--
Ryan
It doesn't need to exactly follow the conditions I used before as long as
Github Actions can provide other good options or conditions.
I just wanted to make sure the condition is reasonable.
2019년 12월 7일 (토) 오전 11:23, Hyukjin Kwon 님이 작성:
> lol how did you know I'm going to read this email Sean?
>
