Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146431530
Fixed failed test Hive test cases by enabling legacy mode explicitly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8945#issuecomment-146436500
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/8945#issuecomment-146436545
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-146449971
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146457243
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
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/8952#discussion_r41490642
--- Diff: R/pkg/R/SQLContext.R ---
@@ -75,8 +75,8 @@ infer_type <- function(x) {
#'\dontrun{
#' sc <- sparkR.init()
#' sqlContext <-
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146465163
From my understanding for some batch workloads like ETL, traditional
process pattern is to read data from HDFS, process and output to HDFS, in such
process pattern
Github user v-gerasimov commented on the pull request:
https://github.com/apache/spark/pull/8056#issuecomment-146465118
Hi, @rxin!
It seems like something wrong when you try to add ```SQLTab``` to
```SparkUI.tabs```, doesn't
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146474747
Fully agree. I'm however not skilled to work on the feature to enable
locality preference and haven't heard about anyone working on it, and the code
as it is now
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-146450878
[Test build #43390 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43390/consoleFull)
for PR 9026 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9010#discussion_r41486700
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/JobScheduler.scala
---
@@ -163,15 +163,35 @@ class JobScheduler(val ssc:
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9010#discussion_r41486775
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/JobScheduler.scala
---
@@ -163,15 +163,35 @@ class JobScheduler(val ssc:
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9010#discussion_r41486855
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/BatchInfo.scala
---
@@ -36,13 +37,10 @@ case class BatchInfo(
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9010#discussion_r41486796
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/Job.scala ---
@@ -29,7 +31,7 @@ class Job(val time: Time, func: () => _) {
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146462053
At some point in the future, very much likely, but it's not happening now
and I'd remove it now (to make the code clearer) and once it's needed it gets
added in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9010#issuecomment-146429491
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
GitHub user admackin opened a pull request:
https://github.com/apache/spark/pull/9025
Akka framesize units should be specified
1.4 docs noted that the units were MB - i have assumed this is still the
case
You can merge this pull request into a Git repository by running:
$ git
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9011#issuecomment-146438339
cc @cloud-fan can you take a look at 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146446097
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146458813
[Test build #43388 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43388/console)
for PR 9024 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146459060
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146459062
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-146460548
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-146460547
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-146460424
[Test build #43390 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43390/console)
for PR 9026 at commit
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/8952#discussion_r41490485
--- Diff: R/pkg/R/SQLContext.R ---
@@ -149,6 +149,26 @@ createDataFrame <- function(sqlContext, data, schema =
NULL, samplingRatio = 1.0
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146468910
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146468890
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 jhu-chang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8881#discussion_r41492611
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/TransformedDStream.scala
---
@@ -17,6 +17,7 @@
package
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8948#issuecomment-146430129
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146430112
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8948
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146430317
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 and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8945#issuecomment-146440195
[Test build #43389 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43389/console)
for PR 8945 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8945#issuecomment-146440227
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8945#issuecomment-146440226
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146446095
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-146445950
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-146445948
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146445979
[Test build #43384 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43384/console)
for PR 7410 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-146445842
[Test build #43383 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43383/console)
for PR 8942 at commit
GitHub user SaintBacchus opened a pull request:
https://github.com/apache/spark/pull/9026
[SPARK-11000][YARN]Bug fix: Derby have booted the database twice in yarn
security mode.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-146449937
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146456998
[Test build #43387 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43387/console)
for PR 8988 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146459679
A-ha so you mean there is a pretty real intent to begin to use this data
structure? enough that we shouldn't remove it?
---
If your project is set up for it, you can
Github user felixmaximilian commented on the pull request:
https://github.com/apache/spark/pull/7647#issuecomment-146461342
I tried this with an instance type where the /root dir isn't on an EBS.
There the volume size parameter hasn't had an effect. It might be a good
extension to
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/8983#issuecomment-146470802
@cloud-fan
Thanks a lot. I have implemented the review comments. Please take a look. I
looked at the optimizer code,. we already seem to be transforming NULL in
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9010#issuecomment-146429251
Screenshot for red dots:
---
If your project is set up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146430096
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/9010#issuecomment-146431457
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9010#issuecomment-146431458
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146431992
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/8988#issuecomment-146432002
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146432044
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146432045
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146432182
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146433122
[Test build #43387 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43387/consoleFull)
for PR 8988 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/9010#discussion_r41482393
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/BatchInfo.scala
---
@@ -36,13 +37,10 @@ case class BatchInfo(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146470783
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/8990#issuecomment-146470805
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
Github user xiaowen147 commented on the pull request:
https://github.com/apache/spark/pull/8943#issuecomment-146474166
@tgravescs @jerryshao @vanzin Thank you for your suggestions. Due to the
YARN's unsupported feature, even if I update, it won't work. So, I consider to
close this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9010#issuecomment-146429481
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/9024
[SPARK-10999] [SQL] Coalesce should be able to handle UnsafeRow
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146429824
@JoshRosen This is the issue we discussed this afternoon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146433852
[Test build #43388 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43388/consoleFull)
for PR 9024 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146438011
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/8881#discussion_r41481193
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/TransformedDStream.scala
---
@@ -17,6 +17,7 @@
package
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146438007
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
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/8881#issuecomment-146439085
LGTM except some small comments :).
---
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/8988#issuecomment-146457244
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146431213
@davies The last build failure was because Hive only recognizes decimals
written as `FIXED_LEN_BYTE_ARRAY`. This might be a good reason for turning
legacy mode on by
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9025#issuecomment-146434046
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8945#issuecomment-146437914
[Test build #43389 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43389/consoleFull)
for PR 8945 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146437957
[Test build #43381 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43381/console)
for PR 8990 at commit
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/8881#discussion_r41481438
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/TransformedDStream.scala
---
@@ -38,6 +39,11 @@ class TransformedDStream[U:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9025
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/9025#issuecomment-14643
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
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/9010#discussion_r41482512
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/JobScheduler.scala
---
@@ -163,15 +163,35 @@ class JobScheduler(val ssc:
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/9010#discussion_r41482427
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/Job.scala ---
@@ -29,7 +31,7 @@ class Job(val time: Time, func: () => _) {
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/8945#issuecomment-146446834
jenkins test 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
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/8881#discussion_r41492868
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/TransformedDStream.scala
---
@@ -17,6 +17,7 @@
package
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146472078
[Test build #43392 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43392/consoleFull)
for PR 8990 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146432177
LGTM as well.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146432740
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/9024#issuecomment-146432768
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
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9010#issuecomment-146449163
overall looks pretty good! I have one main comment that its kind of weird
just expose the `numOuptutOp`. If we have to expose something, we should expose
the whole
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9020#discussion_r41490463
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -512,6 +513,92 @@ object Vectors {
squaredDistance
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146473487
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146473488
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user sridharsubramanian62 commented on the pull request:
https://github.com/apache/spark/pull/6751#issuecomment-146486078
How can this hint be used with Spark-SQL ?
Below example does not seem to work.
```select a.col1,b.col2 from tableA a left outer join
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8993
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146510001
I don't think it causes trouble. Most people don't ever use this
constructor, and using it doesn't cause any problems (well, other than doing
nothing as advertised). If
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8881#discussion_r41495059
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/TransformedDStream.scala
---
@@ -17,6 +17,7 @@
package
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146510564
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146510450
[Test build #43392 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43392/console)
for PR 8990 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146477140
Yeah, but this is also changing the public-facing API. We'd be deprecating
and then undeprecating interfaces, and then potentially deprecating other
interfaces. If this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8993#issuecomment-146492245
[Test build #1858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1858/console)
for PR 8993 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-146492300
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
Github user kevincox commented on the pull request:
https://github.com/apache/spark/pull/8471#issuecomment-146510965
Hello, I was running into the same issue building spark and this patch
fixed my issue. It appears that multiple people are running into this so it
would be nice to
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/8737#issuecomment-146516735
@srowen This problem is not the same with
https://github.com/apache/spark/pull/8945. In this MR, During running tasks,
the AM is failed and restarted. Then the
1 - 100 of 910 matches
Mail list logo
