Skip to content

[SPARK-13257] [Improvement] Scala naive Bayes example: check model after loading - #11192

Closed
movelikeriver wants to merge 2 commits into
apache:masterfrom
movelikeriver:nbscala
Closed

[SPARK-13257] [Improvement] Scala naive Bayes example: check model after loading#11192
movelikeriver wants to merge 2 commits into
apache:masterfrom
movelikeriver:nbscala

Conversation

@movelikeriver

Copy link
Copy Markdown
Contributor

Refine naive Bayes example by checking model after loading it.
This is Java version, to be consistent with Python version in #11125

*/

/*
* Usage:

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.

So this usage text probably isn't the format we want, its pretty specific to each Spark release. Maybe look at some of the other files in this directory and see how they do their usage?

@holdenk

Copy link
Copy Markdown
Contributor

Thanks for taking on this issue & fixing it across multiple languages.

A super minor thing is generally we try and have separate JIRAs for separate PRs - so in this case creating a sub task on the initial PR to also update Scala might be better from a tracking point of view (since when I went to look at this PR my first thought was that the issue had already been resolved).

You might also want to try running the scala linter locally on your code (e.g. ./dev/lint-scala) and make sure it conforms to the style rules.

@HyukjinKwon

Copy link
Copy Markdown
Member

Hi @movelikeriver, are you able to proceed this further? If not, maybe it'd be better closed for now.

@AmplabJenkins

Copy link
Copy Markdown

Can one of the admins verify this patch?

@HyukjinKwonHyukjinKwon mentioned this pull request Feb 15, 2017
zifeif2 pushed a commit to zifeif2/spark that referenced this pull request Nov 22, 2025
## What changes were proposed in this pull request?
This PR proposes to close stale PRs.
What I mean by "stale" here includes that there are some review comments by reviewers but the author looks inactive without any answer to them more than a month.
I left some comments roughly a week ago to ping and the author looks still inactive in these PR below
These below includes some PR suggested to be closed and a PR against another branch which seems obviously inappropriate.
Given the comments in the last three PRs below, they are probably worth being taken over by anyone who is interested in it.
Closesapache#7963Closesapache#8374Closesapache#11192Closesapache#11374Closesapache#11692Closesapache#12243Closesapache#12583Closesapache#12620Closesapache#12675Closesapache#12697Closesapache#12800Closesapache#13715Closesapache#14266Closesapache#15053Closesapache#15159Closesapache#15209Closesapache#15264Closesapache#15267Closesapache#15871Closesapache#15861Closesapache#16319Closesapache#16324Closesapache#16890Closesapache#12398Closesapache#12933Closesapache#14517
## How was this patch tested?
N/A
Author: hyukjinkwon <gurwls223@gmail.com>
Closesapache#16937 from HyukjinKwon/stale-prs-close.
Sign up for freeto 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

@movelikeriver@holdenk@HyukjinKwon@AmplabJenkins