Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-158831881
This is really a good catch, thanks @dilipbiswal
The problems is that, normal operator should be resolved based on its
child, but `Sort` operator can be
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158846758
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/9883#issuecomment-158846761
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/9899
[SPARK-11914] [SQL] Support coalesce and repartition in Dataset APIs
This PR is to provide two common `coalesce` and `repartition` in Dataset
APIs.
After reading the comments of
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158846740
**[Test build #46502 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46502/consoleFull)**
for PR 9883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-158847881
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/6767#issuecomment-158847880
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/6767#issuecomment-158847834
**[Test build #46503 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46503/consoleFull)**
for PR 6767 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9883#discussion_r45571886
--- Diff: sql/catalyst/src/main/scala/org/apache/spark/sql/Row.scala ---
@@ -424,16 +424,34 @@ trait Row extends Serializable {
true
}
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9883#discussion_r45571868
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -45,6 +48,66 @@ case class Md5(child: Expression) extends
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1297#issuecomment-158851260
@josephlijia this feature has moved into a Spark package. If you want to
file an issue report it's best to do it here:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9891#issuecomment-158763431
**[Test build #46490 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46490/consoleFull)**
for PR 9891 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9861#discussion_r45558720
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCRDD.scala
---
@@ -489,6 +492,13 @@ private[sql] class JDBCRDD(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9056#issuecomment-158762298
**[Test build #46487 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46487/consoleFull)**
for PR 9056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158762259
**[Test build #46488 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46488/consoleFull)**
for PR 9883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9892#issuecomment-158774128
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-158774126
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/9891#issuecomment-158762097
**[Test build #46489 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46489/consoleFull)**
for PR 9891 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9056#issuecomment-158764434
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/9056#issuecomment-158764411
**[Test build #46487 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46487/consoleFull)**
for PR 9056 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9056#issuecomment-158764435
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user lresende opened a pull request:
https://github.com/apache/spark/pull/9893
[SPARK-10521][SQL][WIP] Utilize Docker for test DB2 JDBS Dialect support
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lresende/spark
GitHub user lresende opened a pull request:
https://github.com/apache/spark/pull/9892
[SPARK-11910][STREAMING][DOCS] Update twitter4j dependency version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lresende/spark SPARK-11910
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/9891
[SPARK-11908][SQL] Add NullType support to RowEncoder
JIRA: https://issues.apache.org/jira/browse/SPARK-11908
We should add NullType support to RowEncoder.
You can merge this pull request
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-158758320
@ezli this is pretty old now. Do you intend to update it or close it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user CharlesSitbon commented on the pull request:
https://github.com/apache/spark/pull/8112#issuecomment-158743624
@sethah hey, what is the status of that feature ? I expected it to be on
1.6, looking forward to use it.
---
If your project is set up for it, you can reply to
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9876#issuecomment-158758482
Should the client/core versions match up? and be declared as one global
version?
I think using the latest of these is generally a Good Thing, but I know so
many
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9895#issuecomment-158792164
**[Test build #46491 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46491/consoleFull)**
for PR 9895 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9870#discussion_r45563268
--- Diff:
repl/scala-2.10/src/test/scala/org/apache/spark/repl/ReplSuite.scala ---
@@ -315,6 +315,30 @@ class ReplSuite extends SparkFunSuite {
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9890#issuecomment-158792480
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/9895#issuecomment-158792441
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/9890#issuecomment-158792409
**[Test build #46493 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46493/consoleFull)**
for PR 9890 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9890#issuecomment-158792481
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/9895#issuecomment-158792442
Test PASSed.
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/9893#issuecomment-158794747
Jenkins, this is 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
Github user sethah commented on the pull request:
https://github.com/apache/spark/pull/8112#issuecomment-158795213
@CharlesSitbon This PR is still awaiting review from @mengxr. I think it's
too late for this to be in 1.6
---
If your project is set up for it, you can reply to this
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9815#issuecomment-158787457
@gatorsmile Can you create a jira (with repro in the description) and ping
me from that jira?
---
If your project is set up for it, you can reply to this email and have
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9877#discussion_r45562482
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -434,6 +436,24 @@ class Dataset[T] private[sql](
c5: TypedColumn[T,
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9815#issuecomment-158787727
Sorry, I think it is a test case issue.
```
testData = Seq((1, 2), (2, 2), (3, 4), (null.asInstanceOf[Int],
5)).toDF("a", "b")
```
Scala
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/9877#discussion_r45562547
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -434,6 +436,24 @@ class Dataset[T] private[sql](
c5: TypedColumn[T,
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9891
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9815#issuecomment-158787861
oh, i see. Yeah, we need to use `Integer` to get null. `Int` is not
nullable.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9889#issuecomment-158787958
I'm worried the existing caching mechanisms might not work on dataset
operations. Do we have a good notion of equality for encoders and lambda
functions? Can you add
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9890#issuecomment-158787882
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 marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9840#discussion_r45562684
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -124,17 +124,46 @@ object ScalaReflection extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9890#issuecomment-158788602
**[Test build #46493 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46493/consoleFull)**
for PR 9890 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9889#issuecomment-158789433
I see, will make a try. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9702#issuecomment-158789470
**[Test build #46494 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46494/consoleFull)**
for PR 9702 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9877#issuecomment-158790021
**[Test build #46495 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46495/consoleFull)**
for PR 9877 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9891#issuecomment-158775366
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/9891#issuecomment-158775363
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/9891#issuecomment-158775005
**[Test build #46489 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46489/consoleFull)**
for PR 9891 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9895#issuecomment-158779306
**[Test build #46491 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46491/consoleFull)**
for PR 9895 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-158779300
**[Test build #46492 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46492/consoleFull)**
for PR 9894 at commit
Github user lresende commented on the pull request:
https://github.com/apache/spark/pull/9892#issuecomment-158779843
@srowen Sounds good does it look better now ?
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9815#issuecomment-158781004
Thank you @aray @yhuai ! The code changes look great!
Based on my test cases, the rollup and cube still return incorrect results
when the table contains
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9892#discussion_r45560736
--- Diff: docs/streaming-programming-guide.md ---
@@ -723,7 +723,7 @@ Some of these advanced sources are as follows.
- **Kinesis:** Spark Streaming
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158775557
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/9883#issuecomment-158775545
**[Test build #46488 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46488/consoleFull)**
for PR 9883 at commit
GitHub user hhbyyh opened a pull request:
https://github.com/apache/spark/pull/9894
[WIP] [SPARK-11847] [ML] Model export/import for spark.ml: LDA
Add read/write support to LDA, similar to ALS.
save/load for ml.LocalLDAModel is done.
For DistributedLDAModel, I'm not
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/9895
[SPARK-11783][SQL] Fixes execution Hive client when using remote Hive
metastore
When using remote Hive metastore, `hive.metastore.uris` is set to the
metastore URI. However, it overrides
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9815#issuecomment-158781733
This might not be related to rollup logics. It is a bug of Dataframe. I
will try to fix it soon.
Thanks!
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158775556
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/9891#issuecomment-158776794
**[Test build #46490 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46490/consoleFull)**
for PR 9891 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9891#issuecomment-158777032
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/9891#issuecomment-158777051
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/9894#issuecomment-158782005
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/9894#issuecomment-158781971
**[Test build #46492 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46492/consoleFull)**
for PR 9894 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-158782006
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user reggert commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158783297
SparkQA seems to be happy now.
@JoshRosen What else needs to be done to move forward on this? The current
implementation on master requires a dedicated thread pool
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-158795621
**[Test build #46496 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46496/consoleFull)**
for PR 9893 at commit
Github user reggert commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158798727
It appears that this PR may also fix SPARK-4514.
---
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/9264#issuecomment-158799652
**[Test build #46498 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46498/consoleFull)**
for PR 9264 at commit
Github user reggert commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158799901
Correction: This PR only fixes SPARK-4514 as long as the
{{ComplexFutureAction}} only spawns a single job. The job group information is
lost in subsequent jobs.
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158800133
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/9264#issuecomment-158800134
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user reggert commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158800472
I've implemented a two-line fix for SPARK-4514.
---
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/9877#issuecomment-158800570
**[Test build #46495 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46495/consoleFull)**
for PR 9877 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9877#issuecomment-158800614
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/9702#issuecomment-158800720
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/9702#issuecomment-158800694
**[Test build #46494 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46494/consoleFull)**
for PR 9702 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9877#issuecomment-158800613
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/9702#issuecomment-158800719
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/9264#issuecomment-158801223
**[Test build #46499 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46499/consoleFull)**
for PR 9264 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-158807850
**[Test build #46496 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46496/consoleFull)**
for PR 9893 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-158807882
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/9893#issuecomment-158807879
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
101 - 187 of 187 matches
Mail list logo
