Github user uhonnavarkar commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-185122533
I have 2 question below.
1) I have downloaded pre-build version of spark-1.5.2-bin-hadoop2.6.tgz
from spark website(http://spark.apache.org/downloads.html).
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-184814195
@uhonnavarkar, this patch was incorporated into 1.5.1 and 1.6.0, if that's
what you're asking.
---
If your project is set up for it, you can reply to this email and h
Github user uhonnavarkar commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-183873169
Is this problem still exist in Spark 1.5.2 / 1.6.0?
---
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 navis commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-142143125
@rxin It's just a table with 100+ string columns partitioned by a string
key. It happened by a simple query just like select <100+> from where
.
---
If your project is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141520379
@navis can you give us the data type that caused this problem?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141519938
Yes - I cherry-picked it now. 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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141496066
@rxin, should this also go into 1.5.1.?
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8808
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141371836
Thanks - I've merged this.
---
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 th
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141364769
[Test build #1772 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1772/console)
for PR 8808 at commit
[`a26512b`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141347060
[Test build #1772 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1772/consoleFull)
for PR 8808 at commit
[`a26512b`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141314783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141314777
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141309825
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141309836
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 navis opened a pull request:
https://github.com/apache/spark/pull/8808
[SPARK-10684] [SQL] StructType.interpretedOrdering need not to be serialized
Kryo fails with buffer overflow even with max value (2G).
{noformat}
org.apache.spark.SparkException: Kryo seri
16 matches
Mail list logo
