Yup, no worries. I roughly set the one week delay considering the official
release date :D
On Mon, 9 Sep 2019, 09:45 Dongjoon Hyun, wrote:
> Thank you, Hyukjin.
>
> +1 for closing according to 2.3.x EOL.
>
> For the timing, please do that after the official 2.3.4 release
> announcement.
>
>
Thank you, Hyukjin.
+1 for closing according to 2.3.x EOL.
For the timing, please do that after the official 2.3.4 release
announcement.
Bests,
Dongjoon.
On Sun, Sep 8, 2019 at 16:27 Sean Owen wrote:
> I think simply closing old issues with no activity in a long time is
> OK. The "Affected
I’d prefer strict mode and fail fast (analysis check)
Also I like what Alastair suggested about standard clarification.
I think we can re-visit this proposal and restart the vote
From: Ryan Blue
Sent: Friday, September 6, 2019 5:28 PM
To: Alastair Green
Cc:
I think simply closing old issues with no activity in a long time is
OK. The "Affected Version" is somewhat noisy, so not even particularly
important to also query, but yeah I see some value in trying to limit
the scope this way.
On Sat, Sep 7, 2019 at 10:15 PM Hyukjin Kwon wrote:
>
> HI all,
>
A quick question about failure modes, as a casual observer of the DSv2
effort:
I was considering filing a JIRA ticket about enhancing the DataFrameReader
to include the failure *reason* in addition to the corrupt record when the
mode is PERMISSIVE. So if you are loading a CSV, for example, and a
