Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8993#issuecomment-146495414
Merged to master
---
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 jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146506978
Sure, but how do you know **now** how the public API is going to look like?
It is **currently** causing troubles in understanding the code and we only
**wish** /
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-146509549
[Test build #43393 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43393/console)
for PR 8549 at commit
Github user v-gerasimov commented on the pull request:
https://github.com/apache/spark/pull/7774#issuecomment-146475733
Hi, @zsxwing!
It seems like something wrong when you try to add SQLTab to SparkUI.tabs,
doesn't
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/8639#issuecomment-146478502
@rxin @andrewor14 can we get your attention 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8993#issuecomment-146488409
[Test build #1858 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1858/consoleFull)
for PR 8993 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-146492218
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/8549#issuecomment-146497592
[Test build #43393 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43393/consoleFull)
for PR 8549 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-146509643
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/8549#issuecomment-146509644
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/8990#issuecomment-146510565
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7774#issuecomment-146535686
> Hi, @zsxwing!
>
> It seems like something wrong when you try to add SQLTab to SparkUI.tabs,
doesn't
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146564355
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 dragos closed the pull request at:
https://github.com/apache/spark/pull/8671
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146545648
[Test build #43394 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43394/consoleFull)
for PR 9027 at commit
Github user v-gerasimov commented on the pull request:
https://github.com/apache/spark/pull/7774#issuecomment-146539385
@zsxwing Yes, I did. Do you think it is wrong?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146544834
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 jerryshao commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146545328
Yes, as @srowen said, this API is seldom used, and currently we already
marked it as deprecated, also even calling this API will not introduce any
problem, so keeping
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8943#issuecomment-146542075
@xiaowen147 can you clarify, do you just mean its not fully implemented
yet?
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user dragos opened a pull request:
https://github.com/apache/spark/pull/9027
[SPARK-7874][MESOS] Donât allocate more than spark.cores.max in
fine-grained mode.
Currently only coarse-grained mode observes `spark.cores.max`. The
fine-grained mode should follow the same
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146543767
@tnachen @andrewor14 please have a look
---
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/6648#issuecomment-146564323
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 potto007 commented on the pull request:
https://github.com/apache/spark/pull/8533#issuecomment-146526005
Can I suggest that, at the very least, SPARK_LOCAL_HOSTNAME become
documented? I spent several hours trying to find why my latest Spark cluster
was only choosing a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146544863
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7774#issuecomment-146559430
> @zsxwing Yes, I did. Do you think it is wrong?
That's expected. Every SQLContext has a separate tab to track it's own
queries.
---
If your project is set up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146567168
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/8981#issuecomment-146581775
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/8981#issuecomment-146581808
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 v-gerasimov commented on the pull request:
https://github.com/apache/spark/pull/7774#issuecomment-146589821
@zsxwing No, I can't. I have one spark context for different applications
which registers own temp tables with same names. What if we hide SQL tabs in
dropdown
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8438#issuecomment-146589985
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/6648#issuecomment-146567165
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/6648#issuecomment-146572450
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/6648#issuecomment-146572501
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/6648#issuecomment-146578338
Test FAILed.
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/6648#issuecomment-146578278
[Test build #43396 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43396/console)
for PR 6648 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146578396
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/8981#issuecomment-146582447
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8931#discussion_r41531452
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/TungstenAggregationIterator.scala
---
@@ -690,6 +697,9 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8438#issuecomment-146590132
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146566496
[Test build #43395 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43395/consoleFull)
for PR 6648 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146574433
[Test build #43396 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43396/consoleFull)
for PR 6648 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146578224
[Test build #43394 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43394/console)
for PR 9027 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146578332
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/9027#issuecomment-146578393
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 aniro commented on the pull request:
https://github.com/apache/spark/pull/8669#issuecomment-146579493
Can the following be fixed as well?
```
--- a/bin/load-spark-env.sh2015-10-08 14:51:20.874478368 +
+++ b/bin/load-spark-env.sh2015-10-08
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9017#discussion_r41528972
--- Diff: python/pyspark/ml/param/_shared_params_code_gen.py ---
@@ -51,12 +51,12 @@ def _gen_param_header(name, doc, defaultValueStr):
"""
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9002#issuecomment-146581044
test 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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7774#issuecomment-146581482
> @zsxwing Why did you do that? It looks really dirty when I try to use
Spark UI. Maybe Spark UI header isn't a good place for SQL tabs. What do you
think?
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9002#issuecomment-146582708
[Test build #43398 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43398/consoleFull)
for PR 9002 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9002#issuecomment-146581809
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/9002#issuecomment-146581760
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/8981#issuecomment-146583642
[Test build #43399 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43399/consoleFull)
for PR 8981 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8981#issuecomment-146583786
[Test build #43397 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43397/consoleFull)
for PR 8981 at commit
Github user v-gerasimov commented on the pull request:
https://github.com/apache/spark/pull/7774#issuecomment-146564907
@zsxwing Why did you do that? It looks really dirty when I try to use Spark
UI.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146567159
[Test build #43395 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43395/console)
for PR 6648 at commit
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146574566
SPARK-2089 is marked as resolved so any discussion there is done (or am I
mistaken?)
Also, I'm saying that the comments say it's used in YARN while it's
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8981#issuecomment-146583004
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9021#issuecomment-146582988
LGTM.
@vanzin I think maybe we should monitor dual connections. I also found an
issue about the message order. If we run the following code in order,
```
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8981#issuecomment-146583025
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/9002#issuecomment-146592976
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/9002#issuecomment-146592975
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/8999#issuecomment-146600833
I'm merging this to master since this one is trivial.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/9021#issuecomment-146618288
Merging.
---
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
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/9028#issuecomment-146621398
Do I need to create JIRA ?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8887#issuecomment-146623917
[Test build #43403 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43403/consoleFull)
for PR 8887 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-146625057
[Test build #43404 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43404/consoleFull)
for PR 7052 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-146595930
@jaceklaskowski I think you're going to have to back out your API changes
anyway since they aren't compatible. The rest, yeah, no real problem with
updating docs, or
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8931#discussion_r41534622
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/TungstenAggregationIterator.scala
---
@@ -690,6 +697,9 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146603482
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/8771#issuecomment-146603446
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/9023#issuecomment-146608515
cc @felixcheung
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-146608819
cc @sun-rui @falaki
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146608768
[Test build #43401 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43401/consoleFull)
for PR 6648 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9028#issuecomment-146610899
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/9028#issuecomment-146611082
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 tedyu opened a pull request:
https://github.com/apache/spark/pull/9028
Rename NullColumnAccess as NullColumnAccessor
@davies
I think NullColumnAccessor follows same convention for other accessors
You can merge this pull request into a Git repository by running:
Github user da-steve101 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9020#discussion_r41537324
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -512,6 +513,92 @@ object Vectors {
squaredDistance
}
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9021#issuecomment-146617647
> It's because we use a thread pool to call sendRpc.
That too, but it can also happen if you enable multiple connections per
peer
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8920#issuecomment-146620104
Thanks @NarineK for the PR and @sun-rui for reviewing this.
LGTM and merging this
---
If your project is set up for it, you can reply to this email and have
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/8952#discussion_r41538953
--- Diff: R/pkg/R/SQLContext.R ---
@@ -75,8 +75,8 @@ infer_type <- function(x) {
#'\dontrun{
#' sc <- sparkR.init()
#' sqlContext <-
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9028#issuecomment-146622270
Either is fine to me.
---
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/8887#issuecomment-146622425
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/9002#issuecomment-146592814
[Test build #43398 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43398/console)
for PR 9002 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8438#issuecomment-146593585
[Test build #43400 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43400/consoleFull)
for PR 8438 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6751#issuecomment-146595067
It can only be used from the dataframe API.
On Oct 8, 2015 3:20 AM, "sridharsubramanian62"
wrote:
> How can this hint be used
Github user olarayej commented on a diff in the pull request:
https://github.com/apache/spark/pull/8984#discussion_r41534672
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1881,3 +1881,31 @@ setMethod("as.data.frame",
collect(x)
}
)
+
+#' Returns
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9024#issuecomment-146600052
Thanks, I'm merging this to master.
---
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/8999
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8984#issuecomment-146612757
@olarayej Could you bring this PR up to date with master branch ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9028#issuecomment-146612091
[Test build #43402 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43402/consoleFull)
for PR 9028 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-146622522
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/9024
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-146603453
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8997#issuecomment-146613845
@adrian555 Could you bring this up to date with master branch ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9021
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/9028#issuecomment-146620362
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8920
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8887#issuecomment-146620721
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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-146620620
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-146622442
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
101 - 200 of 910 matches
Mail list logo