Skip to content

[Spark18045][MLlib]updated the information sending to usr._2 - #18045

Closed
NewBoLing wants to merge 1 commit into
apache:masterfrom
NewBoLing:master
Closed

[Spark18045][MLlib]updated the information sending to usr._2#18045
NewBoLing wants to merge 1 commit into
apache:masterfrom
NewBoLing:master

Conversation

@NewBoLing

Copy link
Copy Markdown

I think updated information of updateY incorrectly send to source vertice. the original code like the below.
ctx.sendToSrc((updateP, updateY, (err - conf.gamma6 * usr._3) * conf.gamma1))
In fact, usr._2 store pu + |N(u)|^(-0.5)*sum(y).
we have already updated the part of y in usr._2 through sending the message to destination vertex, and this method will effect the part of y in usr._2,
but the part of pu is never updated. so we should send updateP to source vertex not updateY.

What changes were proposed in this pull request?

(Please fill in changes proposed in this fix)

How was this patch tested?

(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Please review http://spark.apache.org/contributing.html before opening a pull request.

I think updated information of updateY incorrectly send to source vertice. the original code like the below.
ctx.sendToSrc((updateP, updateY, (err - conf.gamma6 * usr._3) * conf.gamma1))
In fact, usr._2 store pu + |N(u)|^(-0.5)*sum(y). we have already updated the part of y in usr._2 through sending the message to destination vertex, and this method will effect the part of y in usr._2,
but the part of pu is never updated. so we should send updateP to source vertex not updateY.
@AmplabJenkins

Copy link
Copy Markdown

Can one of the admins verify this patch?

@srowen

Copy link
Copy Markdown
Member

Please read http://spark.apache.org/contributing.html and fix the title
Does it make sense to send updateP twice?
Maybe @ankurdave can return to comment

@NewBoLingNewBoLing changed the title Update SVDPlusPlus.scalaupdated the information sending to usr._2May 23, 2017
@NewBoLingNewBoLing changed the title updated the information sending to usr._2[Spark18045][MLlib]updated the information sending to usr._2May 24, 2017
@srowensrowen mentioned this pull request Jun 7, 2017
@asfgitasfgit closed this in b771fedJun 8, 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, mostly the same instances with apache#18017Closesapache#11459Closesapache#13833Closesapache#13720Closesapache#12506Closesapache#12456Closesapache#12252Closesapache#17689Closesapache#17791Closesapache#18163Closesapache#17640Closesapache#17926Closesapache#18163Closesapache#12506Closesapache#18044Closesapache#14036Closesapache#15831Closesapache#14461Closesapache#17638Closesapache#18222
Added:
Closesapache#18045Closesapache#18061Closesapache#18010Closesapache#18041Closesapache#18124Closesapache#18130Closesapache#12217
Added:
Closesapache#16291Closesapache#17480Closesapache#14995
Added:
Closesapache#12835Closesapache#17141
## How was this patch tested?
N/A
Author: hyukjinkwon <gurwls223@gmail.com>
Closesapache#18223 from HyukjinKwon/close-stale-prs.
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.

3 participants

@NewBoLing@AmplabJenkins@srowen