+1 We had a SparkR fix for CRAN SystemRequirements that will also be good
to get out.
Shivaram
On Fri, May 11, 2018 at 12:34 PM, Henry Robinson wrote:
> https://github.com/apache/spark/pull/21302
>
> On 11 May 2018 at 11:47, Henry Robinson wrote:
>
>> I was
https://github.com/apache/spark/pull/21302
On 11 May 2018 at 11:47, Henry Robinson wrote:
> I was planning to do so shortly.
>
> Henry
>
> On 11 May 2018 at 11:45, Ryan Blue wrote:
>
>> The Parquet Java 1.8.3 release is out. Has anyone started a PR to
I was planning to do so shortly.
Henry
On 11 May 2018 at 11:45, Ryan Blue wrote:
> The Parquet Java 1.8.3 release is out. Has anyone started a PR to update,
> or should I?
>
> On Fri, May 11, 2018 at 7:40 AM, Cody Koeninger
> wrote:
>
>> Sounds good, I'd
The Parquet Java 1.8.3 release is out. Has anyone started a PR to update,
or should I?
On Fri, May 11, 2018 at 7:40 AM, Cody Koeninger wrote:
> Sounds good, I'd like to add SPARK-24067 today assuming there's no
> objections
>
> On Thu, May 10, 2018 at 1:22 PM, Henry Robinson
Sounds good, I'd like to add SPARK-24067 today assuming there's no objections
On Thu, May 10, 2018 at 1:22 PM, Henry Robinson wrote:
> +1, I'd like to get a release out with SPARK-23852 fixed. The Parquet
> community are about to release 1.8.3 - the voting period closes
+1, I'd like to get a release out with SPARK-23852 fixed. The Parquet
community are about to release 1.8.3 - the voting period closes tomorrow -
and I've tested it with Spark 2.3 and confirmed the bug is fixed. Hopefully
it is released and I can post the version change to branch-2.3 before you
Parquet has a Java patch release, 1.8.3, that should pass tomorrow morning.
I think the plan is to get that in to fix a bug with Parquet data written
by Impala.
On Thu, May 10, 2018 at 11:09 AM, Marcelo Vanzin
wrote:
> Hello all,
>
> It's been a while since we shipped 2.3.0
Hello all,
It's been a while since we shipped 2.3.0 and lots of important bug
fixes have gone into the branch since then. I took a look at Jira and
it seems there's not a lot of things explicitly targeted at 2.3.1 -
the only potential blocker (a parquet issue) is being worked on since
a new