Github user HuJiayin commented on the pull request:
https://github.com/apache/spark/pull/7208#issuecomment-118753913
tarekauel
When you want to merge a small modification next time, please tell me,
Chenghao, we can avoid multiple code rebase issues.
---
If your project is set up
Github user HuJiayin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33910514
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -298,3 +299,56 @@ case class
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-118758477
@squito about stage.pendingTask and shuffleMapStage.isAvaiable
for use `isAvailable` to instead of `stage.pendingTask's`, may need more
careful to do with that.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118764208
[Test build #36564 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36564/consoleFull)
for PR 7235 at commit
Github user HuJiayin commented on the pull request:
https://github.com/apache/spark/pull/7214#issuecomment-118767524
you doesn't need to check left or right string are null or not since the
getLevenshteinDistance check if the strings are null or not. Duplicate checks
will make
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7157#issuecomment-118768731
[Test build #36562 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36562/console)
for PR 7157 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7157#issuecomment-118768907
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 project does
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7115#issuecomment-118773371
ok to test
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7234#issuecomment-118777968
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/7115#issuecomment-118779238
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/7236#issuecomment-118780400
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 tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7186#discussion_r33917806
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -211,6 +211,77 @@ case class EndsWith(left:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6906#issuecomment-118798311
[Test build #36568 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36568/consoleFull)
for PR 6906 at commit
Github user ehnalis closed the pull request at:
https://github.com/apache/spark/pull/6671
---
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/6938#issuecomment-118801462
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 nollbit commented on the pull request:
https://github.com/apache/spark/pull/5563#issuecomment-118802799
We've been running this patch in production for a few weeks now. Apart from
the (now fixed) bug where it would not properly decline unused offers, we've
not had any
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/7115#issuecomment-118811387
@rxin, are you sure we have to re-implement the soundex in `UTF8String`? It
probably be faster if we based on the binary directly, but the code seems will
be
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7237#issuecomment-118814691
[Test build #36570 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36570/consoleFull)
for PR 7237 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6938#issuecomment-118802114
[Test build #36569 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36569/consoleFull)
for PR 6938 at commit
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/7195#discussion_r33922508
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -124,6 +124,13 @@ private[spark] class
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7115#discussion_r33922899
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DataFrameFunctionsSuite.scala ---
@@ -197,6 +197,15 @@ class DataFrameFunctionsSuite extends
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7115#discussion_r33922866
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -298,3 +299,24 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118806602
[Test build #36567 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36567/console)
for PR 7227 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118806812
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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7115#discussion_r33923382
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -211,4 +215,57 @@ public boolean equals(final Object other) {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7237#issuecomment-118812886
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/7237#issuecomment-118812680
cc @rxin
---
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/7237
[SPARK-8837][SPARK-7114][SQL] support using keyword in column name
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark parser
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7237#issuecomment-118812806
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/7115#issuecomment-118820796
[Test build #36565 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36565/console)
for PR 7115 at commit
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/4027#discussion_r33919242
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/CoarseMesosSchedulerBackend.scala
---
@@ -109,6 +123,13 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6906#issuecomment-118796564
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/6906#issuecomment-118796657
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 commented on the pull request:
https://github.com/apache/spark/pull/5563#issuecomment-118797780
I tried this on a 2-node Mesos cluster. I confirm that I could use numeric
values, and it worked as expected.
```
spark.mesos.constraints color:2,3
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6938#issuecomment-118801539
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 commented on the pull request:
https://github.com/apache/spark/pull/5563#issuecomment-118800934
This looks good 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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33922581
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -298,3 +299,38 @@ case class
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33922767
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -298,3 +299,56 @@ case class
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7115#discussion_r33923432
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -211,4 +215,57 @@ public boolean equals(final Object other) {
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7226#discussion_r33923826
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -58,6 +58,7 @@ class SqlParser extends AbstractSparkSQLParser
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7237#issuecomment-118815989
[Test build #36570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36570/console)
for PR 7237 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7237#issuecomment-118816000
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/7157#issuecomment-118818752
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/7157#issuecomment-118818821
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/7157#issuecomment-118820434
[Test build #36571 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36571/consoleFull)
for PR 7157 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7115#issuecomment-118820917
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/7226#issuecomment-118822840
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 aloknsingh commented on the pull request:
https://github.com/apache/spark/pull/7064#issuecomment-118762315
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/7038#issuecomment-118763844
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118768516
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/7115#issuecomment-118773907
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 commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118774406
@srlindemann Thanks for fixing this! Could you please file a JIRA and
change the PR title to [SPARK-] [SQL] Fix partition pruning percentage log
message?
---
If
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33915775
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -298,3 +299,56 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118779417
[Test build #36566 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36566/consoleFull)
for PR 7235 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118784234
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 tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33918377
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -165,6 +165,20 @@ public UTF8String toLowerCase() {
return
Github user mvogiatzis commented on the pull request:
https://github.com/apache/spark/pull/7229#issuecomment-118787601
I agree, this is better. Maybe it's worth mentioning in the example that
Existing words with no new values will also be called by `updateStateByKey`
until they
Github user tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33918833
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -165,6 +165,20 @@ public UTF8String toLowerCase() {
return
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118763100
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 guowei2 opened a pull request:
https://github.com/apache/spark/pull/7235
[SPARK-8833][STREAMING] Kafka Direct API support offset in zookeeper
Kafka Direct API support offset in zookeeper
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7064#issuecomment-118762950
[Test build #1000 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1000/consoleFull)
for PR 7064 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-118769448
Yes, Python streaming Kafka related tests will not be run if this jar is
missing.
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118775601
Is this even worth a JIRA? there is virtually no difference between the
description and fix
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7115#issuecomment-118779725
[Test build #36565 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36565/consoleFull)
for PR 7115 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7219#discussion_r33911870
--- Diff: pom.xml ---
@@ -1826,6 +1830,26 @@
/properties
/profile
+profile
+ !--
+ Use this profile
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118771200
[Test build #36564 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36564/console)
for PR 7235 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118771476
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/7064#issuecomment-118774633
[Test build #1000 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1000/console)
for PR 7064 at commit
Github user mvogiatzis commented on the pull request:
https://github.com/apache/spark/pull/7229#issuecomment-118775714
The documentation above states: This can be used to maintain arbitrary
state data for each key .
I would expect that each key means each incoming key in the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118779952
[Test build #36567 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36567/consoleFull)
for PR 7227 at commit
Github user tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33917004
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -298,3 +299,56 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118784082
[Test build #36566 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36566/console)
for PR 7235 at commit
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/4984#discussion_r33918664
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/CoarseMesosSchedulerBackend.scala
---
@@ -285,4 +336,38 @@ private[spark] class
Github user tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33918634
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -165,6 +165,20 @@ public UTF8String toLowerCase() {
return
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118763109
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 guowei2 commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118763116
I will add test case for this 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 does
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7235#discussion_r33912834
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaCluster.scala
---
@@ -402,7 +402,7 @@ object KafkaCluster {
}
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7235#discussion_r33912844
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaUtils.scala
---
@@ -403,12 +405,19 @@ object KafkaUtils {
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7235#discussion_r33912859
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaUtils.scala
---
@@ -403,12 +405,19 @@ object KafkaUtils {
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7235#issuecomment-118767492
CC @koeninger but I don't think this class is intended to manage Kafka
offsets by itself
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-118768088
So some tests have not been running at all? OK well seems to be a good
thing to fix no matter what. Isn't that the headline topic here then -- not
just about consistency
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118773694
ok to test
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118773885
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/7229#issuecomment-118776821
No I mean farther up in UpdateStateByKey Operation where the operation is
explained, rather than putting this as a coda at the end after examples. You
can weave a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7234#issuecomment-118777882
[Test build #36563 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36563/console)
for PR 7234 at commit
Github user HuJiayin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7186#discussion_r33915726
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -211,6 +211,77 @@ case class EndsWith(left:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118779237
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/7235#issuecomment-118779236
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 tarekauel opened a pull request:
https://github.com/apache/spark/pull/7236
[SPARK-8830][SQL] native levenshtein distance
Jira: https://issues.apache.org/jira/browse/SPARK-8830
@rxin and @HuJiayin can you have a look on it.
You can merge this pull request into a
Github user tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7115#discussion_r33917250
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -301,6 +304,31 @@ case class
Github user tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33918209
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -165,6 +165,20 @@ public UTF8String toLowerCase() {
return
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7226#issuecomment-118822880
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/7226#issuecomment-118823364
[Test build #36572 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36572/consoleFull)
for PR 7226 at commit
Github user srlindemann commented on the pull request:
https://github.com/apache/spark/pull/7227#issuecomment-118823372
I saw on one of the contrib pages that trivial changes might not have a
JIRA, so I skipped it here. Happy to do it though if you like.
On Jul 6, 2015 4:38 AM,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7238#issuecomment-118824062
[Test build #36573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36573/consoleFull)
for PR 7238 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/7237#issuecomment-118824058
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/7237#issuecomment-118824886
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/6743#issuecomment-118824907
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 HuJiayin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7208#discussion_r33925319
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -298,3 +299,38 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-118828773
[Test build #36575 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36575/console)
for PR 6743 at commit
1 - 100 of 889 matches
Mail list logo
