Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1911#issuecomment-52012907
QA results for PR 1911:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1882#issuecomment-52013113
QA results for PR 1882:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1884#issuecomment-52013158
QA results for PR 1884:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1907#issuecomment-52013277
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1907#issuecomment-52013347
QA results for PR 1907:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1907#issuecomment-52013468
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1907#issuecomment-52013487
QA tests have started for PR 1907. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18419/consoleFull
---
Github user colorant commented on the pull request:
https://github.com/apache/spark/pull/1884#issuecomment-52013518
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1904#issuecomment-52013574
+@liancheng, @marmbrus I think this is good catch.`SparkSQLCLIDriver` will
resort to `SetProcessor`(of Hive) for all of the `set` command currently, but
with this
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1884#issuecomment-52013620
It's ok the flume test is not related. I am going to merge this in master
branch-1.1.
---
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/1907#issuecomment-52013782
QA tests have started for PR 1907. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18420/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1884#issuecomment-52013783
QA tests have started for PR 1884. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18421/consoleFull
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1884
---
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 mengxr opened a pull request:
https://github.com/apache/spark/pull/1917
[SPARK-3001][MLLIB] Improve Spearman's correlation
The current implementation requires sorting individual columns, which could
be done with a global sort.
You can merge this pull request into a Git
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1846#issuecomment-52014423
Is this my fault? 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1846#issuecomment-52014594
QA tests have started for PR 1846. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18424/consoleFull
---
Github user colorant commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-52014668
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-52014901
QA tests have started for PR 1241. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18425/consoleFull
---
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1892#issuecomment-52015074
Thanks. Merging in master branch-1.1
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1912#discussion_r16159823
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -315,6 +315,15 @@ private[spark] object PythonRDD extends Logging {
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52015135
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1892
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1911#issuecomment-52015369
LGTM. Merged into both master and branch-1.1. Thanks for adding this and
cleaning `MLLibPythonAPI`!!
---
If your project is set up for it, you can reply to this email
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1911
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1917#issuecomment-52015516
Jenkins, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1917#issuecomment-52015796
QA tests have started for PR 1917. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18427/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1917#issuecomment-52015802
QA results for PR 1917:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-52016089
QA tests have started for PR 1031. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18428/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-52016096
QA results for PR 1031:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-52016199
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52016367
QA tests have started for PR 1912. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18430/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1022#issuecomment-52016360
QA tests have started for PR 1022. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18431/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1022#issuecomment-52016370
QA results for PR 1022:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-52016533
QA results for PR 1241:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1917#issuecomment-52016614
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 have
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52016718
I was talking to Jenkins when I said test this please, but thanks @davies
for adding tests too.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1884#issuecomment-52016904
QA results for PR 1884:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1917#issuecomment-52016999
QA tests have started for PR 1917. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18432/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1917#issuecomment-52017008
QA results for PR 1917:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52017380
LoL, I realized this just after pushing the commit :)
---
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/1907#issuecomment-52018299
QA tests have started for PR 1907. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18434/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-52018301
QA tests have started for PR 1241. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18435/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-52018311
QA results for PR 1241:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1907#issuecomment-52018524
QA results for PR 1907:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1846#issuecomment-52018533
QA results for PR 1846:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brcase class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1907#issuecomment-52018958
QA results for PR 1907:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52019343
QA results for PR 1912:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/1889#issuecomment-52019410
I noticed that currently Parquet support can't handle `MapType` containing
`null` value.
There is a following difference, though:
- writing and reading of
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1846#issuecomment-52020897
Seems failed due to some other reasons.
---
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 tsudukim opened a pull request:
https://github.com/apache/spark/pull/1918
[SPARK-3006] Failed to execute spark-shell in Windows OS
Modified the order of the options and arguments in spark-shell.cmd
You can merge this pull request into a Git repository by running:
$
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1918#issuecomment-52023691
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/1907#issuecomment-52024735
QA results for PR 1907:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
GitHub user baishuo opened a pull request:
https://github.com/apache/spark/pull/1919
[SPARK-3007][SQL]Add Dynamic Partition support to Spark Sql hive
the detail please refer the comment of
https://issues.apache.org/jira/browse/SPARK-3007
You can merge this pull request into a Git
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/1920
[SPARK-3004][SQL] Added null checking when retrieving row set
JIRA issue: [SPARK-3004](https://issues.apache.org/jira/browse/SPARK-3004)
HiveThriftServer2 throws exception when the result
Github user baishuo commented on the pull request:
https://github.com/apache/spark/pull/1919#issuecomment-52026271
I didnt have add the related test since I dont know how to write it. but
I had test the function by SparkSQLCLIDriver
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1919#issuecomment-52026260
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/1920#issuecomment-52026411
QA tests have started for PR 1920. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18436/consoleFull
---
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1904#issuecomment-52026786
@guowei2 Are you sure `set spark.sql.shuffle.partitions=n` doesn't work?
Would you mind to provide steps to reproduce this issue? 'Cause I just tried it
with the most
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1891#issuecomment-52026960
Build failure was caused by PySpark again :(
---
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/1891#issuecomment-52026969
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1891#issuecomment-52027298
QA tests have started for PR 1891. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18437/consoleFull
---
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1891#issuecomment-52027481
Oh, actually the build failure was caused by a Spark SQL Python API test
case. It seems that we are comparing floating point numbers directly:
```
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/1878#discussion_r16165816
--- Diff: examples/src/main/python/mllib/random_and_sampled_rdds.py ---
@@ -0,0 +1,88 @@
+#
+# Licensed to the Apache Software Foundation (ASF)
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/1878#discussion_r16165936
--- Diff: examples/src/main/python/mllib/random_and_sampled_rdds.py ---
@@ -0,0 +1,88 @@
+#
+# Licensed to the Apache Software Foundation (ASF)
Github user nrchandan commented on the pull request:
https://github.com/apache/spark/pull/1787#issuecomment-52028983
@pwendell @srowen This version passes all test cases. Also added a new test
case (the one specified in JIRA #SPARK-2862
---
If your project is set up for it, you can
Github user guowei2 commented on the pull request:
https://github.com/apache/spark/pull/1904#issuecomment-52031004
@liancheng it is ok in (HiveThriftServer2 + beeline).
it doesn't work in spark-sql. so does in my develop IDE with running
SparkSQLCLIDriver
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1920#issuecomment-52032154
QA results for PR 1920:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user guowei2 commented on the pull request:
https://github.com/apache/spark/pull/1822#issuecomment-52032345
I've improve the structure and testing. is it 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.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1891#issuecomment-52032913
QA results for PR 1891:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/1889#issuecomment-52033915
Or do we have to make Parquet support be able to handle `null` values now?
Parquet format will change to apply changes.
---
If your project is set up for it, you can
GitHub user YanTangZhai opened a pull request:
https://github.com/apache/spark/pull/1921
[SPARK-3003] FailedStage could not be cancelled by DAGScheduler when
cancelJob or cancelStage
Some stage is changed from running to failed, then DAGSCheduler could not
cancel it when cancelJob
Github user kmader commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-52049280
@freeman-lab looks good, I will add it to this pull request if that's ok
for you. I think my personal preference would be do keep byteFile for standard
operations and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1921#issuecomment-52049448
QA tests have started for PR 1921. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18438/consoleFull
---
GitHub user jacek-lewandowski opened a pull request:
https://github.com/apache/spark/pull/1922
SPARK-3009: Reverted readObject method in ApplicationInfo so that Applic...
...ationInfo is initialized properly after deserialization
You can merge this pull request into a Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1922#issuecomment-52050526
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 scwf opened a pull request:
https://github.com/apache/spark/pull/1923
[SQL]Excess judgment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scwf/spark patch-4
Alternatively you can review and apply these changes as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1923#issuecomment-52052524
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/1923#issuecomment-52053181
(PS excess judgment doesn't quite make sense -- I think you mean
redundant conditional?)
Yes that's redundant although I thought the consensus was not to fix
trivial
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-52053774
QA results for PR 1658:br- This patch FAILED unit tests.brbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-52053578
QA tests have started for PR 1658. This patch DID NOT merge cleanly!
brView progress:
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/1923#issuecomment-52054526
yes, i mean redundant conditional, do you mean we should fix all redundant
conditions ?
---
If your project is set up for it, you can reply to this email and have your
Github user kmader commented on a diff in the pull request:
https://github.com/apache/spark/pull/1658#discussion_r16177677
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -511,6 +511,67 @@ class SparkContext(config: SparkConf) extends Logging {
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-52055084
QA tests have started for PR 1658. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18441/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1921#issuecomment-52055809
QA results for PR 1921:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1891#issuecomment-52062088
@sarutak Just FYI, @yhuai is taking care of the floating-point issue.
Jenkins was pretty crazy during the last 12 hours. We're trying to calm him
down...
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-52062694
QA results for PR 1658:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-52064657
QA tests have started for PR 1031. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18442/consoleFull
---
GitHub user joesu opened a pull request:
https://github.com/apache/spark/pull/1924
[SPARK-3011][SQL] _temporary directory should be filtered out by
sqlContext.parquetFile
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/1924#issuecomment-52069053
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/1916#issuecomment-52070624
@ericgarcia would be great if you could check if this patch works for you?
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/1925
[SQL] Using safe floating-point numbers in doctest
Test code in `sql.py` tries to compare two floating-point numbers directly,
and cased [build
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1925#issuecomment-52071418
QA tests have started for PR 1925. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18443/consoleFull
---
Github user liancheng closed the pull request at:
https://github.com/apache/spark/pull/1925
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/1925#issuecomment-52071469
Closing this since it's already fixed in 882da57. /cc @yhuai
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-52072285
QA results for PR 1031:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1920#issuecomment-52074293
I believe the build failure is caused by
[SPARK-3013](https://issues.apache.org/jira/browse/SPARK-3013). Should retest
this after the issue is fixed.
---
If your
GitHub user liancheng reopened a pull request:
https://github.com/apache/spark/pull/1925
[SQL] Using safe floating-point numbers in doctest
Test code in `sql.py` tries to compare two floating-point numbers directly,
and cased [build
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1925#issuecomment-52074671
After some thoughts, I think we still need to use safer floating-point
numbers (`I/2**J`), since the `2.1...` pattern doesn't cover evil cases like
`2.0999`.
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/1926
Typo in script
use_conf_dir = user_conf_dir in load-spark-env.sh.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WangTaoTheTonic/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1926#issuecomment-52075508
QA tests have started for PR 1926. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18444/consoleFull
---
1 - 100 of 502 matches
Mail list logo
