Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15575
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15575
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67319/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15575
**[Test build #67319 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67319/consoleFull)**
for PR 15575 at commit
Github user wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15541#discussion_r84422357
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskAssigner.scala
---
@@ -0,0 +1,218 @@
+/*
+ * Licensed to the Apache Software
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15568
@mallman , item 4 is a potential problem in the future. The current
workflow is, we get the `MetastoreRelation` via
`HiveMetastoreCatalog.lookupRelation`, which always lower case the database and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14847
**[Test build #67324 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67324/consoleFull)**
for PR 14847 at commit
Github user wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15541#discussion_r84422079
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskAssigner.scala
---
@@ -0,0 +1,218 @@
+/*
+ * Licensed to the Apache Software
Github user zhzhan commented on the issue:
https://github.com/apache/spark/pull/15541
@gatorsmile I didn't see your new comments
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15541#discussion_r84421949
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskAssigner.scala
---
@@ -0,0 +1,218 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13891
**[Test build #67323 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67323/consoleFull)**
for PR 13891 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15568#discussion_r84421537
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/TableFileCatalog.scala
---
@@ -102,6 +95,13 @@ class TableFileCatalog(
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/15319
Thanks @jiangxb1987, this equivalence class approach looks pretty solid.
I'll take a closer look tomorrow!
---
If your project is set up for it, you can reply to this email and have your
Github user hqzizania commented on the issue:
https://github.com/apache/spark/pull/13891
@yanboliang So sorry for my late response.
Some regression performance test results:
Datasets: using
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/15576
Thanks for fixing this! I encountered this issue before.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15541
Accidentally, I deleted all my comments. You might need to check the emails
to find all my comments. :)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user sheepduke commented on the issue:
https://github.com/apache/spark/pull/15579
This is rather useful sometimes because you wan tto add some extra tuning
arguments like 'numactl'.
Otherwise it is not even possible to achieve that.
Yes it only works with YARN for
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15575
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15575
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67318/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15575
**[Test build #67318 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67318/consoleFull)**
for PR 15575 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15579
Please also review
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark
Thanks a lot!
---
If your project is set up for it, you can reply to this email and have your
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15579
This seems really weird to do (and also only works in YARN).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15576
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67321/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15576
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15576
**[Test build #67321 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67321/consoleFull)**
for PR 15576 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15513
Oh, no. I will try to test each when writing the documentation. Please
ignore minor incorrectness here.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15513
Do we have binary literals anyway?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15513
Then I will do as below:
**Literal only**
```
a string literal.
a numeric literal that defines ...
a binary literal that represents ... For example, ...
```
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15513
Sure, sounds great.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15579
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
GitHub user sheepduke opened a pull request:
https://github.com/apache/spark/pull/15579
Added support for extra command in front of spark.
## What changes were proposed in this pull request?
A minor functional change is added into yarn facility to make it possible
for
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15513
How about "a string literal" vs "a string expression"?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15513
Also, will try to consolidate multiple usages and take out `_FUNC_` in
extended part too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15513
@rxin, How about this?
**Literal only**
```
a string type value.
a numeric type value that defines ...
a binary type value that defines ... For example, ...
```
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15551
@rxin : Thanks for notifying me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15569
thanks for the review, merging to master!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15569
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15481
**[Test build #67322 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67322/consoleFull)**
for PR 15481 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15481
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15576
**[Test build #67321 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67321/consoleFull)**
for PR 15576 at commit
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15575
@yhuai : please see the table in this PRs description. I have added a
`comment` (last column) for each entry to point out those cases.
---
If your project is set up for it, you can reply to
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15575
> I felt that there are numerous places where child's output ordering could
be used but the operators don't set it
Can you list them at here?
---
If your project is set up for it, you can
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15576
Rebased. This should pass now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15576
Test failure is intentional, it's picking up the following warnings:
```
Warnings
---
1. createDataFrame uses
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15560
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user wankunde closed the pull request at:
https://github.com/apache/spark/pull/15578
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15560
merged to master and branch-2.0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15575
**[Test build #67320 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67320/consoleFull)**
for PR 15575 at commit
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15575
Agree with the planner behavior described in the last few comments
(relevant code :
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15575
**[Test build #67319 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67319/consoleFull)**
for PR 15575 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67317/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15577
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14079
**[Test build #67317 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67317/consoleFull)**
for PR 14079 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15577
Thanks! Merging to master and 2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15513
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15513
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67314/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15513
**[Test build #67314 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67314/consoleFull)**
for PR 15513 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15513
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67315/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15513
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15513
**[Test build #67315 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67315/consoleFull)**
for PR 15513 at commit
Github user zhzhan commented on the issue:
https://github.com/apache/spark/pull/15541
@rxin Can you please take a look, and let me know if you have any concern?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15513
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15513
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67313/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15513
**[Test build #67313 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67313/consoleFull)**
for PR 15513 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15578
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
GitHub user wankunde opened a pull request:
https://github.com/apache/spark/pull/15578
Branch 2.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wankunde/spark branch-2.0
Alternatively you can review and apply these changes as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14957
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67316/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14957
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15575
Yeah. So I don't see any exception that an unary node, if it is not
`ShuffleExchange`, can have an `outputPartitioning` other than
`child.outputPartitioning`.
---
If your project is set up for it,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14957
**[Test build #67316 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67316/consoleFull)**
for PR 14957 at commit
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15575
Our planner decides if to add an `ShuffleExchange` by consider
`outputPartitioning` and `requiredDistribution` together. If the
`outputPartitioning` of the child does not satisfy the
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15566
Sorry I was wrong. The root cause of SPARK-17990 is that, when we write
data for a hive table, we ignore the truth that hive table is not
case-preserving, and create the partition directory with
Github user vijoshi commented on a diff in the pull request:
https://github.com/apache/spark/pull/15556#discussion_r84413566
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/ReplayListenerBus.scala ---
@@ -43,38 +43,56 @@ private[spark] class ReplayListenerBus extends
Github user lw-lin closed the pull request at:
https://github.com/apache/spark/pull/13507
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user lw-lin commented on the issue:
https://github.com/apache/spark/pull/13507
I'm closing this in favor of SPARK-17924, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15575
**[Test build #67311 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67311/consoleFull)**
for PR 15575 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15575
The query planner will inject exchange based on the required distribution
for the child of `UnaryNodeExec`. Looks like all unary nodes have
`child.outputPartitioning` as its output partition. I
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15575
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67311/
Test PASSed.
---
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15575
@yhuai let me be more clear. It is actually fairly confusing to say "this
only changes if the operator doesn't shuffle data".
The thing is that we are relying on each operator's output
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15575
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15575
**[Test build #67318 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67318/consoleFull)**
for PR 15575 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15575#discussion_r84411683
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/limit.scala ---
@@ -96,13 +95,15 @@ trait BaseLimitExec extends UnaryExecNode with
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15575#discussion_r84411628
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SortExec.scala ---
@@ -45,6 +45,8 @@ case class SortExec(
override def
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15481
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67312/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15481
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15481
**[Test build #67312 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67312/consoleFull)**
for PR 15481 at commit
Github user YuhuWang2002 commented on the issue:
https://github.com/apache/spark/pull/15297
@tgravescs ï¼
Thank you for your response, when a single reduce task handling huge data,
it's slowly and unstable. so we split one reduce task to multi- reduce task.
A single reduce
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15575
`outputPartitioning` of a node will only be changed if this node shuffles
data. Right now, only `ShuffleExchange` shuffles data.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15577
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67310/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15577
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15577
**[Test build #67310 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67310/consoleFull)**
for PR 15577 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/15575#discussion_r84410677
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/limit.scala ---
@@ -96,13 +95,15 @@ trait BaseLimitExec extends UnaryExecNode with
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/15575#discussion_r84410707
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/window/WindowExec.scala
---
@@ -103,6 +103,8 @@ case class WindowExec(
override
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15571
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67307/
Test PASSed.
---
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/15575#discussion_r84410586
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/limit.scala ---
@@ -96,13 +95,15 @@ trait BaseLimitExec extends UnaryExecNode with
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15571
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15571
**[Test build #67307 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67307/consoleFull)**
for PR 15571 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/15575#discussion_r84410162
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SortExec.scala ---
@@ -45,6 +45,8 @@ case class SortExec(
override def
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15566
Actually SPARK-17990 can be fixed in this PR with a little more work. Let
me do it now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/9
Related thought: if the model holds a pointer to its initialModel, then it
will be serialized and shipped along with the model at prediction time. This
will be inefficient for large models and even
1 - 100 of 633 matches
Mail list logo
