Hi All,
I think there are few more updates are added in the design document
compare to last document where few folks has reviewed and provided inputs.,
requesting all experts to review the design document and help us to
baseline the design for the SPIP
'Support SQL streaming' in spark
+1
See note
Tested build from source and running tests.
Also tested SparkR basic - ran more tests in RC1 and checked there was no
change in R since. So I’m ok with that.
Note:
1. Opened https://issues.apache.org/jira/browse/SPARK-26855 on the
SparkSubmitSuite failure - (thanks to Sean’s tip) I
This is super awesome!
From: Shivaram Venkataraman
Sent: Saturday, February 9, 2019 8:33 AM
To: Hyukjin Kwon
Cc: dev; Felix Cheung; Bryan Cutler; Liang-Chi Hsieh; Shivaram Venkataraman
Subject: Re: Vectorized R gapply[Collect]() implementation
Those speedups
The HiveExternalCatalogVersionsSuite is hard to make robust as it
downloads several huge Spark archives. It does try several mirrors and
fall back to archive.apache, but, still, plenty of scope for
occasional errors. We need to keep this restricted to only testing a
few recent Spark versions.
On
FYI: I've been working on stabilizing tests on streaming join and Kafka
continuous mode (they're somewhat coupled with - Kafka continuous mode
fails after porting back commit on streaming join) for branch-2.3, and I
think it's done. https://github.com/apache/spark/pull/23757
2019년 2월 11일 (월) 오전
Hey guys,
We have 381 static functions now (including the deprecated). I am trying to
sort them out by group/tag them.
So far, I have:
Array
Conversion
Date
Math
Trigo (sub group of maths)
Security
Streaming
String
Technical
Do you see more categories? Tags?
Thanks!
jg
—
Jean Georges Perrin
Thanks, Felix,
`-Pkubernetes-integration-tests` doesn't exist in branch-2.3?
Probably, it does in master/branch-2.4.
On Mon, Feb 11, 2019 at 5:51 AM Jungtaek Lim wrote:
> FYI: I've been working on stabilizing tests on streaming join and Kafka
> continuous mode (they're somewhat coupled with -
Yes, looks like there's less usage which needs this change, so it isn't
beneficial to change default. I'll see whether I can address without
touching default.
Thanks all for providing opinions regarding this topic.
2019년 2월 10일 (일) 오전 12:48, Sean Owen 님이 작성:
> If many people find the current
