Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72199/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16753
**[Test build #72199 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72199/testReport)**
for PR 16753 at commit
Github user salilsurendran commented on the issue:
https://github.com/apache/spark/pull/16664
@yhuai @marmbrus @liancheng Can someone review my PR please. 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
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/16757
[SPARK-18609][SQL] Fix redundant Alias removal in the optimizer
## What changes were proposed in this pull request?
The optimizer tries to remove redundant alias only projections from the
Github user klinvill commented on a diff in the pull request:
https://github.com/apache/spark/pull/16746#discussion_r98710451
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/jdbc/TeradataDialect.scala ---
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72200/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16043
**[Test build #72200 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72200/testReport)**
for PR 16043 at commit
Github user limansky commented on the issue:
https://github.com/apache/spark/pull/9759
Hi all. There are security issues in jackson-dataformat-xml prior to 2.7.4
and 2.8.0. Here are the links: FasterXML/jackson-dataformat-xml#199,
FasterXML/jackson-dataformat-xml#190. Even though
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16756
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 does not have this feature
Github user klinvill commented on a diff in the pull request:
https://github.com/apache/spark/pull/16746#discussion_r98706364
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/jdbc/TeradataDialect.scala ---
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16756
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72197/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16756
**[Test build #72197 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72197/testReport)**
for PR 16756 at commit
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/16620#discussion_r98699067
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1212,8 +1223,9 @@ class DAGScheduler(
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/16620#discussion_r98703486
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Stage.scala ---
@@ -68,6 +68,12 @@ private[scheduler] abstract class Stage(
/** Set of jobs
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/16620#discussion_r98703683
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/SchedulerIntegrationSuite.scala
---
@@ -648,4 +660,70 @@ class BasicSchedulerIntegrationSuite
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15009
**[Test build #72201 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72201/consoleFull)**
for PR 15009 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16751
Thank you for review and merging, @viirya , @srowen , and @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
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16620
Hi @jinxing64
sorry to go back and forth on this numerous times -- I think I have another
alternative, see https://github.com/squito/spark/tree/SPARK-19263_alternate
Its most of your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16043
**[Test build #72200 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72200/testReport)**
for PR 16043 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16043
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 feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16753
**[Test build #72199 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72199/testReport)**
for PR 16753 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16043
I am just interested in it :). Yes, this one looks not related 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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16755
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72198/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16755
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16755
**[Test build #72198 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72198/testReport)**
for PR 16755 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72194/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16753
**[Test build #72194 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72194/testReport)**
for PR 16753 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72193/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16753
**[Test build #72193 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72193/testReport)**
for PR 16753 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16755
**[Test build #72198 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72198/testReport)**
for PR 16755 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16756
**[Test build #72197 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72197/testReport)**
for PR 16756 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16603
@mridulm Ok. Thanks for the 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 does not have this feature
enabled
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16756
cc @rxin @liancheng @cloud-fan
---
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
Github user sumitvashistha commented on a diff in the pull request:
https://github.com/apache/spark/pull/15120#discussion_r98669126
--- Diff:
core/src/main/scala/org/apache/spark/internal/config/ConfigProvider.scala ---
@@ -66,7 +66,7 @@ private[spark] class
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/16756
[SPARK-19411][SQL] Remove the metadata used to mark optional columns in
merged Parquet schema for filter predicate pushdown
## What changes were proposed in this pull request?
There is a
GitHub user philipphoffmann opened a pull request:
https://github.com/apache/spark/pull/16755
[MESOS] Support constraints in spark-dispatcher
The `MesosClusterScheduler` doesn't handle the `spark.mesos.constraints`
setting (as opposed to `MesosCoarseGrainedSchedulerBackend`).
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/16043
@HyukjinKwon, @hvanhovell, are you familiar with this build failure? seems
to be unrelated to my specific build...
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16754
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72196/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16754
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16754
**[Test build #72196 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72196/testReport)**
for PR 16754 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16754
**[Test build #72196 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72196/testReport)**
for PR 16754 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72195/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16043
**[Test build #72195 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72195/testReport)**
for PR 16043 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
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 does not have this feature
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/16754
[SPARK-19410][DOC] Fix brokens links in ml-pipeline and ml-tuning
## What changes were proposed in this pull request?
Fix brokens links in ml-pipeline and ml-tuning
`` -> ``
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16043
(Ugh, that -9 again. It is unknown up to my knowledge. I talked about this
before)
---
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 issue:
https://github.com/apache/spark/pull/16043
**[Test build #72195 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72195/testReport)**
for PR 16043 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16735#discussion_r98661043
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVInferSchema.scala
---
@@ -140,12 +137,21 @@ private[csv] object
Github user eyalfa commented on a diff in the pull request:
https://github.com/apache/spark/pull/16043#discussion_r98660310
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/ComplexTypes.scala
---
@@ -0,0 +1,166 @@
+/*
+ * Licensed to the
Github user eyalfa commented on a diff in the pull request:
https://github.com/apache/spark/pull/16043#discussion_r98660085
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/expressions.scala
---
@@ -293,6 +293,12 @@ object SimplifyConditionals extends
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/16043
@hvanhovell can you figure out what fail the build? seems all tests 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 mridulm commented on the issue:
https://github.com/apache/spark/pull/16603
LGTM, will wait for @vanzin's comments before commiting in case he has any.
---
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 issue:
https://github.com/apache/spark/pull/16753
**[Test build #72194 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72194/testReport)**
for PR 16753 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16753
**[Test build #72193 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72193/testReport)**
for PR 16753 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72192/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16753
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16753
**[Test build #72192 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72192/testReport)**
for PR 16753 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16753
@srowen, I see. Let me maybe give a shot to make them consistent to show if
it look good.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16747
I am OK but I remember there are some discussions about whether this type
should be exposed or not and I could not track down the conclusion.
---
If your project is set up for it, you can
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16747
@HyukjinKwon is this OK by you?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16751
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72191/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16751
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16751
**[Test build #72191 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72191/testReport)**
for PR 16751 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16751
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16751
Merging in master.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16750
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16750
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72190/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16750
**[Test build #72190 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72190/testReport)**
for PR 16750 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16751
LGTM too.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16753
**[Test build #72192 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72192/testReport)**
for PR 16753 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16753
It's true, though I wonder if it's still by design, that these methods take
url and table as important first-class arguments, and then also other options,
even though the options also contain the
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16753
Hi @gatorsmile, could you take a look for this one please? (It might not
need a JIRA but it happened to be opened by someone).
---
If your project is set up for it, you can reply to this email
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/16753
[SPARK-19296][SQL] Deduplicate arguments in JdbcUtils.saveTable
## What changes were proposed in this pull request?
This PR deduplicates arguments, `url` and `table` in `JdbcUtils`.
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98624418
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -329,7 +332,17 @@ class DataFrameReader private[sql](sparkSession:
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98629735
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -329,7 +332,17 @@ class DataFrameReader private[sql](sparkSession:
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98625766
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVOptions.scala
---
@@ -161,12 +163,3 @@ private[csv] class
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98623217
--- Diff: python/pyspark/sql/readwriter.py ---
@@ -297,7 +300,7 @@ def text(self, paths):
def csv(self, path, schema=None, sep=None,
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16751
The dependency change looks clear.
---
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 kishorbp closed the pull request at:
https://github.com/apache/spark/pull/16752
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16752
Hi @kishorbp , it seems mistakenly open. Would you please close this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16752
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 project does not have this
GitHub user kishorbp opened a pull request:
https://github.com/apache/spark/pull/16752
Branch 2.0
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how this patch
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16281
Hi, all.
Now, I'm trying to upgrade Apache Spark to 1.8.2.
---
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 issue:
https://github.com/apache/spark/pull/16751
**[Test build #72191 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72191/testReport)**
for PR 16751 at commit
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/16751
[SPARK-19409][BUILD] Bump parquet version to 1.8.2
## What changes were proposed in this pull request?
Apache Parquet 1.8.2 is released officially last week on 26 Jan.
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16689#discussion_r98615769
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1138,6 +1138,11 @@ setMethod("collect",
if (!is.null(PRIMITIVE_TYPES[[colType]]) && colType
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72189/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14412
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14412
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72187/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13932
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72188/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13932
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16750
**[Test build #72190 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72190/testReport)**
for PR 16750 at commit
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16043#discussion_r98613798
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/ComplexTypes.scala
---
@@ -0,0 +1,166 @@
+/*
+ * Licensed to the
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/16750
[SPARK-18937][SQL] Timezone support in CSV/JSON parsing
## What changes were proposed in this pull request?
This is a follow-up pr of #16308.
This pr enables timezone support in
301 - 399 of 399 matches
Mail list logo
