Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8811#issuecomment-149918250
I think the main problem is: we interpret column name with special handling
of `.` for DataFrame. This enables us to write something like `df("a.b")` to
get the field
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-149919454
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8461#issuecomment-149919453
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-149919423
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8461#issuecomment-149919666
**[Test build #44065 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44065/consoleFull)**
for PR 8461 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-149899904
**[Test build #44064 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44064/consoleFull)**
for PR 9055 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9184#issuecomment-149906067
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9184#issuecomment-149906069
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9184#issuecomment-149905864
**[Test build #44061 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44061/consoleFull)**
for PR 9184 at commit
Github user jleach4 commented on the pull request:
https://github.com/apache/spark/pull/5999#issuecomment-149928765
Is there a similar way for this to work using the Java API?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8461#issuecomment-149907689
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8461#issuecomment-149907685
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-149911447
Thank you @JoshRosen so much for the detail review, but seems bug exists,
I'd like to solve it myself soon.
---
If your project is set up for it, you can reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-149922732
**[Test build #44066 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44066/consoleFull)**
for PR 8026 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-149898000
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
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-149907407
Thank you @yhuai for reviewing this.
I've added some more docs for this PR, hopefully make more sense.
First, I'll agree with you to make a general
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8461#issuecomment-149919054
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8461#issuecomment-149919417
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
Github user jlamcanopy commented on the pull request:
https://github.com/apache/spark/pull/6213#issuecomment-149928598
@debasish83 How this is looking? I want to try it soon :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-149897980
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
Github user mariusvniekerk commented on the pull request:
https://github.com/apache/spark/pull/9137#issuecomment-149907705
I'll add tests once #8101 is merged in
---
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/8461#issuecomment-149907622
**[Test build #44063 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44063/consoleFull)**
for PR 8461 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9180#issuecomment-149924728
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9180#issuecomment-149925442
**[Test build #44067 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44067/consoleFull)**
for PR 9180 at commit
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/9175#discussion_r42635685
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -353,10 +353,15 @@ class DAGScheduler(
if
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/9175#discussion_r42635696
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -353,10 +353,15 @@ class DAGScheduler(
if
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9210#issuecomment-150105131
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9193#issuecomment-150105205
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9210#issuecomment-150105203
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9210#issuecomment-150105216
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9193#issuecomment-150105217
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9216#issuecomment-150111409
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9216#issuecomment-150111429
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150111413
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9194#issuecomment-150111307
**[Test build #44131 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44131/consoleFull)**
for PR 9194 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150111428
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
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9217#discussion_r42713149
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/UnsafeRowWriter.java
---
@@ -100,19 +100,27 @@ public void
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9212#issuecomment-150104498
**[Test build #44120 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44120/consoleFull)**
for PR 9212 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9212#issuecomment-150105503
cc @marmbrus
---
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/9217#issuecomment-150111032
**[Test build #44132 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44132/consoleFull)**
for PR 9217 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9216#issuecomment-150111043
Can you add a regression 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150110605
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9217#issuecomment-150110560
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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9216#issuecomment-15017
Actually, maybe we don't need 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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9216#issuecomment-15028
Jenkins, this is ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9217#issuecomment-150112350
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9003#issuecomment-150105959
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9003#issuecomment-150105958
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9003#issuecomment-150105932
**[Test build #44119 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44119/consoleFull)**
for PR 9003 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9210#issuecomment-150106021
**[Test build #44127 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44127/consoleFull)**
for PR 9210 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9215#issuecomment-150100797
**[Test build #44126 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44126/consoleFull)**
for PR 9215 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9212#issuecomment-150104569
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9212#issuecomment-150104570
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/9179#issuecomment-150106716
@shivaram, documentation updated.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9217#issuecomment-150110604
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150110564
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
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9215
[SPARK-11253][SQL] reset all accumulators in physical operators before
execute an action
With this change, our query execution listener can get the metrics
correctly.
You can merge this pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9215#issuecomment-150100164
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9215#issuecomment-150100155
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
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6790#issuecomment-150103961
Actually @marmbrus and I have a discussion on this long time ago, the
conclusion was we'd better to consider the worst case, to avoid the OOM, the
default `0.2`
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/9216
[SPARK-8658] [SQL] AttributeReference's equals method compares all the
members
This fix is to change the equals method to check all of the specified
fields for equality of AttributeReference.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9216#issuecomment-150105599
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/9193#issuecomment-150105522
**[Test build #44128 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44128/consoleFull)**
for PR 9193 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9194#issuecomment-150109737
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9194#issuecomment-150109722
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
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/9217
[SPARK-11243] [SQL] zero out padding bytes in UnsafeRow
For nested StructType, the underline buffer could be used for others
before, we should zero out the padding bytes for those primitive types
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/9192#discussion_r42711959
--- Diff: R/pkg/R/SQLContext.R ---
@@ -17,6 +17,34 @@
# SQLcontext.R: SQLContext-driven functions
+#' Temporary function to reroute old
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9198#issuecomment-150112063
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150112266
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150112265
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9203#discussion_r42711166
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/UnsafeRowWriter.java
---
@@ -58,6 +58,10 @@ private void
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/9193#issuecomment-150105010
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9203#discussion_r42711131
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/UnsafeRowWriter.java
---
@@ -95,41 +99,75 @@ public void
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9179#issuecomment-150108213
LGTM. Thanks @sun-rui -- Will merge after Jenkins passes
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9179#issuecomment-150107792
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9179#issuecomment-150107736
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9194#issuecomment-150114075
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9209#issuecomment-150104101
**[Test build #1936 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1936/consoleFull)**
for PR 9209 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150111480
**[Test build #1937 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1937/consoleFull)**
for PR 8829 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-150111554
**[Test build #44135 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44135/consoleFull)**
for PR 8829 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9194#issuecomment-150114052
**[Test build #44131 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44131/consoleFull)**
for PR 9194 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9180#issuecomment-149939754
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149960061
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9198#issuecomment-149960056
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9194#issuecomment-149960034
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9194#issuecomment-149960057
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149960020
> Test build #44062 has finished for PR 9197 at commit a3246e5.
>
> This patch fails from timeout after a configured wait of `250m`.
> This patch merges
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9198#issuecomment-149960024
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149961297
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149961349
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9180#issuecomment-149939452
**[Test build #44067 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44067/consoleFull)**
for PR 9180 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9180#issuecomment-149939755
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-149941344
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-149941345
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149950246
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149950155
**[Test build #44062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44062/consoleFull)**
for PR 9197 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149950241
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9197#issuecomment-149962448
**[Test build #44072 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44072/consoleFull)**
for PR 9197 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8880#issuecomment-149942075
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
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-149963999
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
1 - 100 of 778 matches
Mail list logo
