Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/17739
Because I don't have the environment to continue this work, I will close
it. Thanks.
---
-
To unsubscribe, e-mail: reviews-unsubsc
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76998/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76998/testReport)**
for PR 17739 at commit
[`e0d6daa`](https://github.com/apache/spark/commit/e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76998 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76998/testReport)**
for PR 17739 at commit
[`e0d6daa`](https://github.com/apache/spark/commit/e0
Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/17739
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, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76971/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76971 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76971/testReport)**
for PR 17739 at commit
[`e0d6daa`](https://github.com/apache/spark/commit/e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76971 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76971/testReport)**
for PR 17739 at commit
[`e0d6daa`](https://github.com/apache/spark/commit/e0
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
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
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76787/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76787 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76787/testReport)**
for PR 17739 at commit
[`ffe79b8`](https://github.com/apache/spark/commit/f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76787 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76787/testReport)**
for PR 17739 at commit
[`ffe79b8`](https://github.com/apache/spark/commit/ff
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76781/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76781 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76781/testReport)**
for PR 17739 at commit
[`cbd2402`](https://github.com/apache/spark/commit/cb
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76775/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76775 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76775/testReport)**
for PR 17739 at commit
[`85f6c1d`](https://github.com/apache/spark/commit/8
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76775 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76775/testReport)**
for PR 17739 at commit
[`85f6c1d`](https://github.com/apache/spark/commit/85
Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/17739
Hi @MLnick , since #17742 is merged into branch-2.2, and this PR is related
with PR17742. Should we close this PR and open a new PR based on branch-2.2.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76108/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76108 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76108/testReport)**
for PR 17739 at commit
[`b4e392e`](https://github.com/apache/spark/commit/b
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76108 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76108/testReport)**
for PR 17739 at commit
[`b4e392e`](https://github.com/apache/spark/commit/b4
Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/17739
Thanks @MLnick . Could you please review my another PR for recommend all
performance problem.
https://github.com/apache/spark/pull/17742.
Sorry, I forget user cannot call recommendForAll direct
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/17739
It's interesting to see the performance difference. I've also been looking
at performance of recommend all but haven't gotten to varying the block sizes
just yet.
I'm potentially in favor of
Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/17739
RecommandProductsForUsers. 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 feature
enabled and
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/17739
ok. And it is the timing for `recommendProductsForUsers`? Or
`recommendUsersForProducts`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/17739
users is 480,000, items is 170,000. 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 feature
en
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/17739
Or is it 48,000 and 1,700?
---
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 wishe
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/17739
Just to confirm, the #users is 48 million, #items is 1.7 million?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17739
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76096/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17739
**[Test build #76096 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76096/testReport)**
for PR 17739 at commit
[`78e060e`](https://github.com/apache/spark/commit/78
36 matches
Mail list logo
