Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8955#issuecomment-144644388
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 maxwellzdm opened a pull request:
https://github.com/apache/spark/pull/8955
[SPARK-5569] [STREAMING] fix ObjectInputStreamWithLoader for supporting
load array classes.
When use Kafka DirectStream API to create checkpoint and restore saved
checkpoint when restart,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-144645064
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/8922#issuecomment-144645045
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/8922#issuecomment-144646240
[Test build #43147 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43147/consoleFull)
for PR 8922 at commit
Github user smola commented on the pull request:
https://github.com/apache/spark/pull/8746#issuecomment-144693706
@sabhyankar Great! The implementation looks good. Could you add a test case
for it?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8956#issuecomment-144701972
[Test build #43149 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43149/consoleFull)
for PR 8956 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8385#issuecomment-144707850
@nssalian I'd like to resolve this at last. This has outstanding comments
and needs a rebase. Do you want to do that or should I take over?
---
If your project is set
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8893#issuecomment-144707576
It looks like @chenghao-intel is farther along towards a simpler fix in
https://github.com/apache/spark/pull/8933/files Do you mind closing this PR?
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8956#issuecomment-144726375
[Test build #43149 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43149/console)
for PR 8956 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/8956
[SPARK-10895][SQL] Push down string filters to Parquet
JIRA: https://issues.apache.org/jira/browse/SPARK-10895
You can merge this pull request into a Git repository by running:
$ git pull
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8949#issuecomment-144708587
Per comments in the JIRA, I think this is unnecessary as you can use the
standard Maven syntax to build modules correctly. Do you mind closing this PR?
---
If your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8951#issuecomment-144708911
Do you mind closing 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 does not
Github user nssalian commented on the pull request:
https://github.com/apache/spark/pull/8385#issuecomment-144723093
@srowen please go ahead.
Thank you.
---
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/8956#issuecomment-144726522
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/8956#issuecomment-144726518
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-144697959
ping @liancheng @marmbrus
---
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/8956#issuecomment-144700733
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144706624
Yeah, the current script does blindly 'pass' the first arg as an
environment variable. It never parsed any args at all to the arg-parsing code,
which seems like an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8956#issuecomment-144700717
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-144707186
@KaiXinXiaoLei do you mind closing 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8881#issuecomment-144707086
[Test build #1833 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1833/consoleFull)
for PR 8881 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8737#issuecomment-144707252
@KaiXinXiaoLei are you working on this, or else do you mind closing this
PR? I'm also not clear if it's the same thing as
https://github.com/apache/spark/pull/8945
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8881#issuecomment-144707377
[Test build #1833 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1833/console)
for PR 8881 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-144732292
[Test build #43150 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43150/consoleFull)
for PR 8954 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144738730
Aha you're right about "1". It can stay:
```
usage="Usage: spark-daemon.sh [--config ]
(start|stop|submit|status) "
```
Yes it doesn't pass args now but
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8946
---
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 akatz opened a pull request:
https://github.com/apache/spark/pull/8957
[SPARK-10889] [Streaming] Bump KCL to add MillisBehindLatest metric
I don't believe the API changed at all.
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-144734249
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/8954#issuecomment-144734253
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/8958
[SPARK-10900][Streaming]Add output operation events to StreamingListener
Add output operation events to StreamingListener so as to implement the
following UI features:
1. Progress bar of a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8957#issuecomment-144731855
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144732338
You guys are misinterpreting the script.
That `1` is not an argument to the HistoryServer, it's an argument to
`spark-daemon.sh`. The script never passes any
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-144733008
@JoshRosen #8775
---
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/8946#issuecomment-144738827
Merged to master and branch-1.5, 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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144740121
The change in `start-history-server.sh` adds the command line parameters,
and those are propagated to the java process. That part of the change is fine.
The
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144741977
Good, yes passing through the args is right. Right now if you run
`start-history-server.sh foo` you will successfully set the log directory to
foo because of what the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8958#issuecomment-144754459
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/8958#issuecomment-144754489
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/8958#issuecomment-14475
/cc @tdas
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8958#issuecomment-144756156
[Test build #43151 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43151/consoleFull)
for PR 8958 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-144730502
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/8954#issuecomment-144730473
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8946#issuecomment-144732736
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-144734228
[Test build #43150 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43150/console)
for PR 8954 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144742060
Hmm, I think I get what you're trying to do. You're trying to implement the
script's command line handling in `HistoryServerArguments` (the old `if [ $# !=
0 ]; then`
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144749562
Hi, me again. Looking at the code once more, I think it's ok if you want to
make this change in the scala code and not the shell script (so, e.g., you can
unit test it),
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8958#issuecomment-144771166
[Test build #43151 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43151/console)
for PR 8958 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8952#issuecomment-144788137
Yeah that would be great.
---
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 jayantshekhar closed the pull request at:
https://github.com/apache/spark/pull/8951
---
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
Github user jayantshekhar commented on the pull request:
https://github.com/apache/spark/pull/8951#issuecomment-144787366
Thanks Sean! Closing it.
---
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/8941#issuecomment-144790511
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/8952#issuecomment-144782174
Thanks @NarineK - I left some inline comments regarding the roxygen docs.
Regarding the sqlContext reuse, I think we should do that in a separate JIRA.
Could you file
Github user NarineK commented on the pull request:
https://github.com/apache/spark/pull/8952#issuecomment-144787827
Hi Shivaram,
should I change the example for createDataFrame with iris too ?
Thanks
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8952#issuecomment-144790493
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/8941#issuecomment-144790574
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/8952#issuecomment-144790538
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-144776282
I will post performance comparison later.
---
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 shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/8952#discussion_r40933250
--- Diff: R/pkg/R/SQLContext.R ---
@@ -149,6 +149,26 @@ createDataFrame <- function(sqlContext, data, schema =
NULL, samplingRatio = 1.0
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-144772135
I'm a little skeptical that this is worth the complexity. Do you have real
works loads that this speeds up significantly?
---
If your project is set up for it, you
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/8952#discussion_r40933374
--- 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/8958#issuecomment-144771352
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/8958#issuecomment-144771351
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/8952#issuecomment-144792949
[Test build #43152 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43152/consoleFull)
for PR 8952 at commit
Github user NarineK commented on the pull request:
https://github.com/apache/spark/pull/8952#issuecomment-144794849
Here is the jira for making sqlContext global.
https://issues.apache.org/jira/browse/SPARK-10903
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8952#issuecomment-144796830
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 tijoparacka commented on the pull request:
https://github.com/apache/spark/pull/8554#issuecomment-144803543
yu-iskw could you please reivew 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/8941#issuecomment-144803339
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 felixcheung commented on the pull request:
https://github.com/apache/spark/pull/8952#issuecomment-144816142
looks good.
---
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/8959#issuecomment-144818093
Hi @tgravescs ,
This fixes the problem but I think it's actually just masking a subtle bug
elsewhere. In `getUserClasspath`, there's this code:
val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8941#issuecomment-144792979
[Test build #43153 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43153/consoleFull)
for PR 8941 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8957#issuecomment-144793932
[Test build #1834 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1834/consoleFull)
for PR 8957 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8899#issuecomment-144794227
@navis can you follow up on this PR or close it?
---
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/8952#issuecomment-144796688
[Test build #43152 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43152/console)
for PR 8952 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-144796916
I like that better since it focuses narrowly on supporting one arg.
@rekhajoshm what do you think? the rest looks good.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8952#issuecomment-144796833
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/8909#issuecomment-144798668
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/8959#issuecomment-144810614
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/8959#issuecomment-144810576
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/8909#issuecomment-144812918
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/8909#issuecomment-144812883
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8959#issuecomment-144821230
where are you suggesting putting this .map so its clear? in getUserPath on
mainUri? I'm not seeing how your map call fixes anything so I"m guessing I'm
missing
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8957#issuecomment-144793663
Seems OK to me, but the usual question is simply, does it introduce any
potential problems too? changes dependencies, incompatible behavior, etc? might
skim the release
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8909#issuecomment-144797066
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/8909#issuecomment-144797039
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/8909#issuecomment-144799890
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/8909#issuecomment-144799919
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/8941#issuecomment-144803367
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 tijoparacka commented on the pull request:
https://github.com/apache/spark/pull/8554#issuecomment-144803700
@yu-iskw could you please reivew 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/8941#issuecomment-144805650
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/8941#issuecomment-144805491
[Test build #43153 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43153/console)
for PR 8941 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8941#issuecomment-144805646
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8959#issuecomment-144812185
[Test build #43157 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43157/consoleFull)
for PR 8959 at commit
Github user tijoparacka commented on the pull request:
https://github.com/apache/spark/pull/8532#issuecomment-144802854
Any of you can review this and merge. I may loose track if it is delayed
more.
---
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/8941#issuecomment-144804910
[Test build #43156 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43156/consoleFull)
for PR 8941 at commit
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/8385#discussion_r40947175
--- Diff: docs/running-on-yarn.md ---
@@ -16,37 +16,51 @@ containers used by the application use the same
configuration. If the configurat
Java system
Github user olarayej commented on the pull request:
https://github.com/apache/spark/pull/8920#issuecomment-144809819
@shivaram @felixcheung @sun-rui Thanks for your feedback!
I totally see your point with the naming (sort vs. arrange), but @NarineK's
implementation has two
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8909#issuecomment-144816852
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8909#issuecomment-144798664
[Test build #43154 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43154/console)
for PR 8909 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8909#issuecomment-144798673
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 309 matches
Mail list logo
