Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added the PrefixSpan MLlib example based on the current documentation #15344

Closed
wants to merge 2 commits into from

Conversation

rangeonnicolas
Copy link

What changes were proposed in this pull request?

Added the PrefixSpan MLlib example based on the current documentation

How was this patch tested?

with this command line :
./bin/spark-submit ./examples/src/main/python/mllib/prefix_span_example.py

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@holdenk
Copy link
Contributor

holdenk commented Oct 5, 2016

Thanks @rangeonnicolas for taking the effort to improve our Python MLlib documentation :)
For this to show up in the documentation you will also need to update the ./docs/mllib-frequent-pattern-mining.md file.

After you'e done that you can verify the new docs locally following the steps in ./docs/README.md :)

@holdenk
Copy link
Contributor

holdenk commented Nov 4, 2016

Hi @rangeonnicolas are you still interested in working on this change?

@rangeonnicolas
Copy link
Author

Yes, I'm doing it!

2016-11-04 1:02 GMT+01:00 Holden Karau notifications@github.com:

Hi @rangeonnicolas https://github.com/rangeonnicolas are you still
interested in working on this change?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15344 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHRuT24SGy5AJsCqBbL2tQPmboudHeKdks5q6nX7gaJpZM4KN0lX
.

@rangeonnicolas
Copy link
Author

I think it's done, But I didn't managed to test the doc. github doens't not display it well

@holdenk
Copy link
Contributor

holdenk commented Nov 29, 2016

Ah yes, testing the documentation can be a bit difficult. You can take a look at the guide under docs/README.md to see how to build the documentation locally and verify it looks like you expect it to. Let me know how that goes and we can try and find a committer to take a look at this.

@maropu maropu mentioned this pull request Apr 23, 2017
maropu added a commit to maropu/spark that referenced this pull request Apr 23, 2017
@asfgit asfgit closed this in e9f9715 Apr 24, 2017
peter-toth pushed a commit to peter-toth/spark that referenced this pull request Oct 6, 2018
This pr proposed to close stale PRs. Currently, we have 400+ open PRs and there are some stale PRs whose JIRA tickets have been already closed and whose JIRA tickets does not exist (also, they seem not to be minor issues).

// Open PRs whose JIRA tickets have been already closed
Closes apache#11785
Closes apache#13027
Closes apache#13614
Closes apache#13761
Closes apache#15197
Closes apache#14006
Closes apache#12576
Closes apache#15447
Closes apache#13259
Closes apache#15616
Closes apache#14473
Closes apache#16638
Closes apache#16146
Closes apache#17269
Closes apache#17313
Closes apache#17418
Closes apache#17485
Closes apache#17551
Closes apache#17463
Closes apache#17625

// Open PRs whose JIRA tickets does not exist and they are not minor issues
Closes apache#10739
Closes apache#15193
Closes apache#15344
Closes apache#14804
Closes apache#16993
Closes apache#17040
Closes apache#15180
Closes apache#17238

N/A

Author: Takeshi Yamamuro <yamamuro@apache.org>

Closes apache#17734 from maropu/resolved_pr.

Change-Id: Id2e590aa7283fe5ac01424d30a40df06da6098b5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants