+1 This will be a great long-term investment for Spark.
On Wed, Feb 6, 2019 at 8:44 AM Marco Gaido wrote:
> +1 from me as well.
>
> Il giorno mer 6 feb 2019 alle ore 16:58 Yanbo Liang
> ha scritto:
>
>> +1 for the proposal
>>
>>
>>
>> On Thu, Jan 31, 2019 at 12:46 PM Mingjie Tang wrote:
>>
+1, too.
branch-2.4 accumulates too many commits..:
https://github.com/apache/spark/compare/0a4c03f7d084f1d2aa48673b99f3b9496893ce8d...af3c7111efd22907976fc8bbd7810fe3cfd92092
On Tue, Feb 12, 2019 at 12:36 PM Dongjoon Hyun wrote:
> Thank you, DB.
>
> +1, Yes. It's time for preparing 2.4.1
Thank you, DB.
+1, Yes. It's time for preparing 2.4.1 release.
Bests,
Dongjoon.
On 2019/02/12 03:16:05, Sean Owen wrote:
> I support a 2.4.1 release now, yes.
>
> SPARK-23539 is a non-trivial improvement, so probably would not be
> back-ported to 2.4.x.SPARK-26154 does look like a bug whose
I support a 2.4.1 release now, yes.
SPARK-23539 is a non-trivial improvement, so probably would not be
back-ported to 2.4.x.SPARK-26154 does look like a bug whose fix could
be back-ported, but that's a big change. I wouldn't hold up 2.4.1 for
it, but it could go in if otherwise ready.
On Mon,
Hi DB,
Could you add SPARK-23539[^1] into 2.4.1? I opened the PR[^2] a little bit
ago, but it has not included in 2.3.0 nor get enough review.
Thanks,
Dongjin
[^1]: https://issues.apache.org/jira/browse/SPARK-23539
[^2]: https://github.com/apache/spark/pull/22282
On Tue, Feb 12, 2019 at 6:28
Given SPARK-26154 [1] is a correctness issue and PR [2] is submitted, I
hope it can be reviewed and included within Spark 2.4.1 - otherwise it will
be a long-live correctness issue.
Thanks,
Jungtaek Lim (HeartSaVioR)
1. https://issues.apache.org/jira/browse/SPARK-26154
2.
Hello all,
I am preparing to cut a new Apache 2.4.1 release as there are many bugs and
correctness issues fixed in branch-2.4.
The list of addressed issues are
+1. Ran our regression tests for YARN and Hive, all look good.
On Tue, Feb 5, 2019 at 5:07 PM Takeshi Yamamuro wrote:
>
> Please vote on releasing the following candidate as Apache Spark version
> 2.3.3.
>
> The vote is open until February 8 6:00PM (PST) and passes if a majority +1
> PMC votes
I will reiterate some feedback I left on the PR. Firstly, it’s not immediately
clear if we should be opinionated around supporting GPUs in the Docker image in
a first class way.
Firstly there’s the question of how we arbitrate the kinds of customizations we
support moving forward. For
Hi Jean,
I thought the functions have already been tagged?
Pozdrawiam,
Jacek Laskowski
https://about.me/JacekLaskowski
Mastering Spark SQL https://bit.ly/mastering-spark-sql
Spark Structured Streaming https://bit.ly/spark-structured-streaming
Mastering Kafka Streams
what do you mean by ''Tungsten Consumer"?
On Fri, Feb 8, 2019 at 6:11 PM Jack Kolokasis
wrote:
> Hello all,
> I am studying about Tungsten Project and I am wondering when Spark
> creates a Tungsten consumer. While I am running some applications, I see
> that Spark creates Tungsten Consumer
11 matches
Mail list logo
