Correction: the SPIP is https://issues.apache.org/jira/browse/SPARK-24359
--Hossein
On Tue, May 22, 2018 at 6:23 PM, Hossein wrote:
> Hi all,
>
> SparkR supports calling MLlib functionality with an R-friendly API. Since
> Spark 1.5 the (new) SparkML API which is based on
Hi all,
SparkR supports calling MLlib functionality with an R-friendly API. Since
Spark 1.5 the (new) SparkML API which is based on pipelines and parameters
has matured significantly. It allows users build and maintain complicated
machine learning pipelines. A lot of this functionality is
Starting with my own +1. Did the same testing as RC1.
On Tue, May 22, 2018 at 12:45 PM, Marcelo Vanzin wrote:
> Please vote on releasing the following candidate as Apache Spark version
> 2.3.1.
>
> The vote is open until Friday, May 25, at 20:00 UTC and passes if
> at least
Please vote on releasing the following candidate as Apache Spark version 2.3.1.
The vote is open until Friday, May 25, at 20:00 UTC and passes if
at least 3 +1 PMC votes are cast.
[ ] +1 Release this package as Apache Spark 2.3.1
[ ] -1 Do not release this package because ...
To learn more
Hi,
I'm wondering why are the metrics repeated in FileSourceScanExec.metrics
[1] since it is a ColumnarBatchScan [2] and so inherits the two
metrics numOutputRows and scanTime from ColumnarBatchScan.metrics [3].
Shouldn't FileSourceScanExec.metrics be as follows then:
override lazy val
I opened a PR - https://github.com/apache/spark/pull/21399 to run it with
SBT.
2018-05-22 2:18 GMT+08:00 Reynold Xin :
> Can we look into if there is a plugin for sbt that works and then we can
> put everything into one single builder?
>
> On Mon, May 21, 2018 at 11:17 AM
I’m in the same exact boat as Maximiliano and have use cases as well for model
serving and would love to join this discussion.
Sent from my iPhone
On May 22, 2018, at 6:39 AM, Maximiliano Felice
> wrote:
Hi!
I'm don't usually
Hi!
I'm don't usually write a lot on this list but I keep up to date with the
discussions and I'm a heavy user of Spark. This topic caught my attention,
as we're currently facing this issue at work. I'm attending to the summit
and was wondering if it would it be possible for me to join that
I’m with you on json being more readable than parquet, but we’ve had
success using pyarrow’s parquet reader and have been quite happy with it so
far. If your target is python (and probably if not now, then soon, R), you
should look in to it.
On Mon, May 21, 2018 at 16:52 Joseph Bradley
Hi,
we went through a round of reviews on this PR. Performance improvements
can be substantial and there are unit and performance tests included.
One remark was that the amount of changed code is large but I don't see
how to reduce it and still keep the performance improvements. Besides,
10 matches
Mail list logo