Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/735
---
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 if the feature is
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-50657401
Thanks for the update, Koert!
@pwendell @rxin after this, what do you guys think of lowering the initial
buffer size to 1 MB or 512K? We've had some efforts to
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-49250226
Jenkins, retest this please. @koertkuipers mind creating a JIRA for this
(we're trying to track all changes now). I can merge this in once we have an
issue for it.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-49250323
QA tests have started for PR 735. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16760/consoleFull
---
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-49251684
https://issues.apache.org/jira/browse/SPARK-2543
On Wed, Jul 16, 2014 at 9:53 PM, Apache Spark QA notificati...@github.com
wrote:
QA tests
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-49254912
QA results for PR 735:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user mingyukim commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-48544943
Hi all, is there any update on this PR?
---
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
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-48548156
i updated docs and defaults as requested. currently waiting for feedback or
a merge
On Wed, Jul 9, 2014 at 6:46 PM, mingyukim
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-48176100
Jenkins, 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-48176282
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-48176269
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-48181546
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16372/
---
If your project
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46865956
not sure if i am supposed to deal with these failures?
On Sat, Jun 21, 2014 at 1:52 PM, UCB AMPLab notificati...@github.com
wrote:
Refer to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46759314
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46759318
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46760188
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15984/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46760187
Merged build finished.
---
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
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46716428
hey sorry somehow misses this conversation thread. sure will update
defaults and docs
On Wed, Jun 4, 2014 at 1:48 AM, Patrick Wendell
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-45053682
@koertkuipers any interest in updating the docs and bumping the default?
This would be a good change to have.
---
If your project is set up for it, you can reply to
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-44501123
Hey one other thought, is there a reason to have the max this low? It might
be good to make it even higher to deal with the odd large object (e.g. people
working with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-43040453
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-43040447
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-43042030
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-43042031
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14960/
---
If your project
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-42896061
hey matei,
i think they always had this feature in kryo, at least in 2.x.
created jira here:
https://issues.apache.org/jira/browse/SPARK-1811
GitHub user koertkuipers opened a pull request:
https://github.com/apache/spark/pull/735
Feat kryo max buffersize
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tresata/spark feat-kryo-max-buffersize
Alternatively you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-42785049
Can one of the admins verify this patch?
---
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
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-42789917
Hey, so is this a new feature that was recently added to Kryo? Seems super
useful, but in this case, I'd actually make the max buffer size higher by
default. Or we can use
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-42789924
Jenkins, this is ok to test
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-42789966
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-42791202
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-42791203
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14895/
---
If your project
32 matches
Mail list logo
