Skip to content

[DOCS][ML][SPARK-11964] Add in Pipeline Import/Export Documentation - #10179

Closed
bllchmbrs wants to merge 20 commits into
apache:masterfrom
bllchmbrs:master
Closed

[DOCS][ML][SPARK-11964] Add in Pipeline Import/Export Documentation#10179
bllchmbrs wants to merge 20 commits into
apache:masterfrom
bllchmbrs:master

Conversation

@bllchmbrs

Copy link
Copy Markdown
Contributor

Adding in Pipeline Import and Export Documentation.

@bllchmbrs

Copy link
Copy Markdown
Contributor Author

not sure if my notations are correct for the title @jkbradley, let me know if I need to change anything!

@jkbradley

Copy link
Copy Markdown
Member

Can you please add "[ML]" to the PR title? And also edit the first comment in the PR to describe what the PR is doing (since it will become part of the commit message)? I'll review it now, thanks!

@jkbradley

Copy link
Copy Markdown
Member

Oh also please remove "SPARK-6725" from the PR title. It's better to have a 1 JIRA - 1 PR correspondence.

Comment thread docs/ml-guide.md Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"for later use" instead of "for usage later" sounds better to me.
"In Spark 1.6, a model import/export" instead of "similar"
"ML models"

@BenFradet

Copy link
Copy Markdown
Contributor

A few minor comments on the documentation, but otherwise it lgtm.

@jkbradley

Copy link
Copy Markdown
Member

This is really similar to the existing Pipeline examples...as it probably should be. However, that makes me wonder if the best way to do this would be to:

  • Add a very small text description subsection at the end of the "Main concepts in Pipelines" section.
  • Modify one of the existing code examples to include save/load.

That should simplify the PR a lot. Thanks!

@bllchmbrs bllchmbrs changed the title [DOCS][SPARK-11964][SPARK-6725] Add in Pipeline Import/Export Documentation [DOCS][ML][SPARK-11964] Add in Pipeline Import/Export Documentation Dec 7, 2015
@bllchmbrs

Copy link
Copy Markdown
Contributor Author

@jkbradley will make those changes shortly.

@BenFradet will make those changes as well.

@bllchmbrs

Copy link
Copy Markdown
Contributor Author

@jkbradley does this work for you by the way?

Comment thread docs/ml-guide.md Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a model import/export functionality...

@BenFradet

Copy link
Copy Markdown
Contributor

LGTM except one minor comment.

@bllchmbrs

Copy link
Copy Markdown
Contributor Author

@BenFradet integrated your feedback thanks.

@jkbradley

Copy link
Copy Markdown
Member

@anabranch Hm, I may not have been clear enough. The save/load functionality seems general and important enough that it should go under the "Main concepts in Pipelines" section; I would put a subsection with a small paragraph (without code) at the end of the "Main concepts in Pipelines" section, just before the "Code example" section. I would then modify the first code example "Example: Estimator, Transformer, and Param" to include saving and loading the pipeline. Thanks!

@bllchmbrs

Copy link
Copy Markdown
Contributor Author

@jkbradley gotcha! I misinterpreted your last comments, my fault.

One thing I'm confused about though is that the Estimator, Transformer, and Param section doesn't seem to mention pipelines explicitly, more focusing on those components themselves. It doesn't necessarily seem like the best place to talk about pipeline persistence? I'm sure there's just something that I'm missing.

I've updated to move it into the pipeline section but please let me know if you would like me to change it. to the params one and demo it more as a feature. Will be available tomorrow so I can turn it around quickly!

Comment thread docs/ml-guide.md Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would avoid unneeded changes like this since they can cause conflicts.

Comment thread docs/ml-guide.md Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for this

@jkbradley

Copy link
Copy Markdown
Member

Thanks for the updates! Just minor comments now.

I agree we need to improve and reorganize the sections explaining Pipelines; we're working on that in some separate PRs.

@bllchmbrs

Copy link
Copy Markdown
Contributor Author

@jkbradley should be good to go! Sorry for being such a pain!

Comment thread docs/ml-guide.md Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this and next line

I like the idea in this & the next line, but I'd remove this since it will cause problems if users blindly copy and paste the code into a spark shell.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to be crystal clear, you would like me to remove 470 - 472? The "equivalently" bit, right?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes (470-471). I'd keep the newline in 472. Thanks!

@jkbradley

Copy link
Copy Markdown
Member

No, no problem. Just 1 more comment left

@bllchmbrs

Copy link
Copy Markdown
Contributor Author

@jkbradley should be good to go now!

@jkbradley

Copy link
Copy Markdown
Member

LGTM pending tests.
Thanks!

@SparkQA

SparkQA commented Dec 11, 2015

Copy link
Copy Markdown

Test build #2206 has finished for PR 10179 at commit 10ccc22.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):\n * class ExecutorClassLoader(\n

@jkbradley

Copy link
Copy Markdown
Member

Merging with master and branch-1.6

@asfgit asfgit closed this in aa305dc Dec 11, 2015
asfgit pushed a commit that referenced this pull request Dec 11, 2015
Adding in Pipeline Import and Export Documentation.

Author: anabranch <wac.chambers@gmail.com>
Author: Bill Chambers <wchambers@ischool.berkeley.edu>

Closes #10179 from anabranch/master.

(cherry picked from commit aa305dc)
Signed-off-by: Joseph K. Bradley <joseph@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants