Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135394871
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135394838
[Test build #41685 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41685/console)
for PR 8484 at commit
[`9e118c2`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135392861
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135392980
One thing to note is that, case sensitivity of Spark SQL is configurable
([see here] [1]). So I don't think we should make `StructType` completely case
insensitive (ye
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135392859
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135392719
[Test build #41684 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41684/console)
for PR 8483 at commit
[`70c8f7b`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135389447
[Test build #41685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41685/consoleFull)
for PR 8484 at commit
[`9e118c2`](https://gith
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135388747
@srowen , mind taking a look ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135388439
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135388498
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 have
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135387576
/cc @JoshRosen @davies
---
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 viirya opened a pull request:
https://github.com/apache/spark/pull/8484
[SPARK-10065][SQL] Avoid triple copying of var-length objects in Array in
tungsten projection
JIRA: https://issues.apache.org/jira/browse/SPARK-10065
Currently we do unnecessary copying of o
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135386761
[Test build #41684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41684/consoleFull)
for PR 8483 at commit
[`70c8f7b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135384520
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135384552
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 have
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/8483
REMOVE spark.akka.failure-detector.threshold
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CodingCat/spark SPARK_10315
Alternatively you ca
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8482#issuecomment-135378312
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 pr
GitHub user romansew opened a pull request:
https://github.com/apache/spark/pull/8482
SPARK-10314 [CORE]RDD persist to OFF_HEAP tachyon got block rdd_x_x nâ¦
SPARK-10314 [CORE]RDD persist to OFF_HEAP tachyon got block rdd_x_x not
found exception when parallelism is big than data sp
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135376440
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135376437
[Test build #41683 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41683/console)
for PR 8458 at commit
[`02c64eb`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135376439
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135376204
[Test build #41683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41683/consoleFull)
for PR 8458 at commit
[`02c64eb`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135375375
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135375355
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135374158
[Test build #41682 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41682/consoleFull)
for PR 8481 at commit
[`2b414e4`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135374076
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135374072
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135373958
[Test build #41677 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41677/console)
for PR 7520 at commit
[`a389746`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135373539
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135373540
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135373462
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135373483
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 have
Github user zerosign commented on the pull request:
https://github.com/apache/spark/pull/1297#issuecomment-135373104
Hi Ankur,
Any update on this pull request ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135371382
[Test build #41681 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41681/consoleFull)
for PR 8464 at commit
[`22e7bc0`](https://gith
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8479
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135370363
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135370350
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135370380
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135370354
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 h
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38080354
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/local/LocalNodeTest.scala
---
@@ -0,0 +1,192 @@
+/*
+* Licensed to the Apache Softwa
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/8481
[SPARK-SQL] [MINOR] Fixes typo in non-public HiveContext method name
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark hive-cont
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8479#issuecomment-135369577
[Test build #1696 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1696/console)
for PR 8479 at commit
[`b6c17e7`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135368942
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135368946
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135368814
[Test build #41676 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41676/console)
for PR 8464 at commit
[`62b8d24`](https://github.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8446
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8447
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8445
---
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 enab
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8451#issuecomment-135366571
The other sibling PRs look good and I can merge them. This looks good after
the `Strings` change.
---
If your project is set up for it, you can reply to this email and h
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8480#issuecomment-135366372
Yes, I think that commit was to pass style checks though. I assume this
doesn't fail anything? I mean, I don't mind just merging this, but in my
personal opinion I'd like
Github user ihainan commented on the pull request:
https://github.com/apache/spark/pull/8480#issuecomment-135365303
@srowen Thanks for your suggestion.
There was a [similar
commit](https://github.com/apache/spark/commit/7f7505d8db7759ea46e904f767c23130eff1104a)
before and I
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8396#discussion_r38078235
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -107,30 +107,21 @@ object DateTimeUtils {
}
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8468
---
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 enab
Github user CHOIJAEHONG1 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7494#discussion_r38078086
--- Diff: R/pkg/inst/tests/test_sparkSQL.R ---
@@ -417,6 +417,32 @@ test_that("collect() and take() on a DataFrame return
the same number of rows an
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8395#issuecomment-135364212
LGTM, I'm going to merge for 1.6 shortly
---
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 d
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8480#issuecomment-135363484
I think this is too trivial even for a PR. This doesn't fail style checks
right? this isn't worth everyone's cycles.
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8480#issuecomment-135362602
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 pr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8479#issuecomment-135360870
[Test build #1696 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1696/consoleFull)
for PR 8479 at commit
[`b6c17e7`](https://git
GitHub user ihainan opened a pull request:
https://github.com/apache/spark/pull/8480
[Core] whitespace fixes in RangePartitioner
Just a trivial change so I didn't create a corresponding JIRA issue.
You can merge this pull request into a Git repository by running:
$ git pull htt
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8479#issuecomment-135360179
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 an
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38076739
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/local/LocalNodeTest.scala
---
@@ -0,0 +1,192 @@
+/*
+* Licensed to the Apache Soft
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8479#issuecomment-135344885
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 pr
GitHub user jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/8479
[SPARK-9613] [HOTFIX] Fix usage of JavaConverters removed in Scala 2.11
Fix for
[JavaConverters.asJavaListConverter](http://www.scala-lang.org/api/2.10.5/index.html#scala.collection.JavaConve
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8118#issuecomment-135342852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8118#issuecomment-135342851
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8118#issuecomment-135342743
[Test build #41679 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41679/console)
for PR 8118 at commit
[`53f97b7`](https://github.
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135341231
@JoshRosen All tests have passed. Is it ok to merge this to `master`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135339027
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135339028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135338925
[Test build #41673 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41673/console)
for PR 7883 at commit
[`54365fc`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135335342
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135335344
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135335340
[Test build #41678 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41678/console)
for PR 8458 at commit
[`9b5bd05`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135335070
[Test build #41678 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41678/consoleFull)
for PR 8458 at commit
[`9b5bd05`](https://gith
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8471#discussion_r38070986
--- Diff: sql/hive/pom.xml ---
@@ -36,6 +36,12 @@
+
+
+ org.scala-lang
+ scala-library
+ 2.10.3
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8118#issuecomment-135334169
[Test build #41679 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41679/consoleFull)
for PR 8118 at commit
[`53f97b7`](https://gith
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135334139
Ok. Thanks. Wait for @liancheng's review.
---
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 holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/8471#discussion_r38070839
--- Diff: sql/hive/pom.xml ---
@@ -36,6 +36,12 @@
+
+
+ org.scala-lang
+ scala-library
+ 2.10.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135333184
[Test build #41677 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41677/consoleFull)
for PR 7520 at commit
[`a389746`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8118#issuecomment-135332594
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8118#issuecomment-135332651
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135332579
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135332612
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 have
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135332239
@liancheng have more insights on this part.
---
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 projec
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/8118#issuecomment-135331572
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 hav
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-135331297
Yeah, I think the question is, what's the need / motivation? I don't see
this being used in the code. If it's just because it sounds useful, I'm not
sure that's enough ju
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8471#discussion_r38070493
--- Diff: sql/hive/pom.xml ---
@@ -36,6 +36,12 @@
+
+
+ org.scala-lang
+ scala-library
+ 2.10.3
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135329490
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135329544
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 have
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135329004
@zhzhan @chenghao-intel Thanks for comment. I've updated the PR title and
codes. Please check if it is ok for you.
---
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/8472#issuecomment-135328818
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135325048
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135325053
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135324209
Also we need to change
private lazy val nameToField: Map[String, StructField] = fields.map(f =>
f.name.toLowerCase -> f).toMap
---
If your project is set up for i
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135324139
[Test build #41676 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41676/consoleFull)
for PR 8464 at commit
[`62b8d24`](https://gith
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135324085
@zhzhan Looks like it should work.
---
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 no
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135323382
@viirya Take a quick second look at the issue. As @chenghao-intel
mentioned, since normalizing the name(to lower case) is the default behavior.
Should we fix it in the
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135323018
Should be `StandardStructObjectInspector` instead of
`StructObjectInspector` to perform [the
normalization](https://github.com/apache/hive/blob/ac755ebe26361a4647d53db2a2
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135322451
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135322491
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 have
501 - 600 of 604 matches
Mail list logo
