Github user stanzhai closed the pull request at:
https://github.com/apache/spark/pull/7393
---
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 en
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7393#issuecomment-121523359
@stanzhai This PR has been already merged but accidentally, this PR is
still open.
Do you mind closing this PR manually?
---
If your project is set up for it, you c
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7393#issuecomment-121164819
Yeah your'e right about that. I usually rely on the merge commits
referenced in the PR 'documenting' where it was merged, but that isn't
happening now, and maybe isn't ob
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7393#issuecomment-121161545
Actually @srowen has already merged it.
Sean - if you merge something in the future, mind leaving a comment in the
pull request? It is especially useful when the sy
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7393#issuecomment-121160762
Thanks - merging this in master & branch-1.4.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7393#issuecomment-121156328
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7393#issuecomment-121156192
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 pr
GitHub user stanzhai opened a pull request:
https://github.com/apache/spark/pull/7393
[SPARK-9010][Documentation]Improve the Spark Configuration document about
`spark.kryoserializer.buffer`
The meaning of spark.kryoserializer.buffer should be "Initial size of
Kryo's serialization b
Github user stanzhai closed the pull request at:
https://github.com/apache/spark/pull/7368
---
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 en
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7368#issuecomment-121153355
@stanzhai this needs to be opened vs `master` not a branch. Can you close
this PR and replace it?
---
If your project is set up for it, you can reply to this email and h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7368#issuecomment-121070258
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 pr
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7368#issuecomment-120864274
LGTM
---
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 an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7368#issuecomment-120854002
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 pr
GitHub user stanzhai opened a pull request:
https://github.com/apache/spark/pull/7368
[SPARK-9010][Documentation]Improve the Spark Configuration document about
`spark.kryoserializer.buffer`
The meaning of spark.kryoserializer.buffer should be "Initial size of
Kryo's serialization b
14 matches
Mail list logo
