Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18164
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
enabled and wishes so, or if the
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18014#discussion_r119808220
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/OnHeapColumnVector.java
---
@@ -386,6 +425,35 @@ public void putArray(int rowId,
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18183#discussion_r119807397
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ParquetDictionary.java
---
@@ -0,0 +1,51 @@
+/*
+ * Licensed to the
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18183#discussion_r119807273
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ParquetDictionary.java
---
@@ -0,0 +1,51 @@
+/*
+ * Licensed to the
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18183#discussion_r119807101
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/Dictionary.java
---
@@ -0,0 +1,31 @@
+/*
+ * Licensed to the Apache
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18164
@HyukjinKwon Yes, I think it's okay to add 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 project does not have this
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18164#discussion_r119805698
--- Diff: python/pyspark/sql/tests.py ---
@@ -1697,40 +1697,56 @@ def test_fillna(self):
schema = StructType([
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/18164#discussion_r119805293
--- Diff: python/pyspark/sql/tests.py ---
@@ -1697,40 +1697,56 @@ def test_fillna(self):
schema = StructType([
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18164#discussion_r119804978
--- Diff: python/pyspark/sql/tests.py ---
@@ -1697,40 +1697,56 @@ def test_fillna(self):
schema = StructType([
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18164
@ueshin, do you think it is okay to add this? I want to help review here if
so.
---
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 ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18164#discussion_r119800727
--- Diff: python/pyspark/sql/tests.py ---
@@ -1697,40 +1697,56 @@ def test_fillna(self):
schema = StructType([
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/18164#discussion_r119800139
--- Diff: python/pyspark/sql/tests.py ---
@@ -1697,40 +1697,56 @@ def test_fillna(self):
schema = StructType([
Github user rberenguel commented on a diff in the pull request:
https://github.com/apache/spark/pull/18164#discussion_r119798778
--- Diff: python/pyspark/sql/tests.py ---
@@ -1697,40 +1697,56 @@ def test_fillna(self):
schema = StructType([
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18181
**[Test build #77673 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77673/testReport)**
for PR 18181 at commit
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
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 liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
Unfortunately, rolling back parquet-mr to 1.8.1 brings back
[PARQUET-389][1], which breaks multiple test cases involving schema evolution
(add a new column to a Parquet table and filter on that
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18183#discussion_r119796465
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ParquetDictionary.java
---
@@ -0,0 +1,51 @@
+/*
+ * Licensed to the
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18164#discussion_r119791032
--- Diff: python/pyspark/sql/tests.py ---
@@ -1697,40 +1697,56 @@ def test_fillna(self):
schema = StructType([
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18130
There's a [JIRA](https://issues.apache.org/jira/browse/SPARK-20650)
planning to remove this `JobProgressListener`, so I'd suggest to not change
this deprecated code unnecessarily.
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18185
**[Test build #77672 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77672/testReport)**
for PR 18185 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18185
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 this feature
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18184
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77670/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18184
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77668/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77669/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18184
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/18185
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77671/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
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/18184
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/18185
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/18183
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/18183
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77667/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18183
**[Test build #77667 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77667/testReport)**
for PR 18183 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18185
**[Test build #77671 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77671/testReport)**
for PR 18185 at commit
GitHub user maropu opened a pull request:
https://github.com/apache/spark/pull/18185
[SPARK-20962][SQL] Support subquery column aliases in FROM clause
## What changes were proposed in this pull request?
This pr added parsing rules to support subquery column aliases in FROM
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18184
**[Test build #77670 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77670/testReport)**
for PR 18184 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18174
I don't think that addresses my question? when would you set this
separately?
---
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/18181
**[Test build #77669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77669/testReport)**
for PR 18181 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18184
**[Test build #77668 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77668/testReport)**
for PR 18184 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18184
cc @cloud-fan @sameeragarwal @ueshin
---
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 liyichao commented on the issue:
https://github.com/apache/spark/pull/18070
How about Letting TaskCommitDenied and TaskKilled extend a same trait (for
example, TaskKilledReason)? This way when accounting metrics, TaskCommitDenied
and TaskKilled are all contributing to
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/18184
[MINOR] [SQL] Update the description of spark.sql.files.ignoreCorruptFiles
### What changes were proposed in this pull request?
When the file does not exist, we will issue the error
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
@viirya Thanks for reminding! I'm reverting that one.
---
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 liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
@dongjoon-hyun I already reverted PR #16751 manually but forgot to mention
it in the PR description.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18128#discussion_r119788377
--- Diff: R/pkg/inst/tests/testthat/test_mllib_classification.R ---
@@ -225,6 +225,32 @@ test_that("spark.logit", {
model2 <- spark.logit(df2,
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18128#discussion_r119787497
--- Diff: R/pkg/R/mllib_classification.R ---
@@ -239,21 +253,57 @@ function(object, path, overwrite = FALSE) {
setMethod("spark.logit",
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18128#discussion_r119788169
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/r/LogisticRegressionWrapper.scala ---
@@ -97,7 +97,15 @@ private[r] object LogisticRegressionWrapper
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18148
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/18148
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77666/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77666 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77666/testReport)**
for PR 18148 at commit
Github user pralabhkumar commented on the issue:
https://github.com/apache/spark/pull/18118
12d83aa is successful . Please review the pull request .
@MLnick @sethah @mpjlu @srowen
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user catlain commented on the issue:
https://github.com/apache/spark/pull/14783
still have this issue when input data is a array column with different
length each vector, like:
```
test1
key value
1 4dda7d68a202e9e3
301 - 351 of 351 matches
Mail list logo
