Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17711#discussion_r116044119
--- Diff: sql/core/src/test/resources/sql-tests/inputs/operators.sql ---
@@ -32,3 +32,11 @@ select 1 - 2;
select 2 * 5;
select 5 % 3;
selec
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17712
---
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 ena
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17917
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17917
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76817/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17917
**[Test build #76817 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76817/testReport)**
for PR 17917 at commit
[`1a0e49e`](https://github.com/apache/spark/commit/1
Github user ndimiduk commented on the issue:
https://github.com/apache/spark/pull/17006
Close the PR you mean? That's fine, I'm afraid I won't be able to make this
a priority in the near term. Please don't close the JIRA though -- this is a
big problem.
---
If your project is set up
Github user ndimiduk closed the pull request at:
https://github.com/apache/spark/pull/17006
---
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 e
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/17894
Would you mind adding `[WIP]` to the title? Without even a benchmark for
dense features, this is definitely a work-in-progress.
---
If your project is set up for it, you can reply to this email and
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17712
Thanks! Merging to 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 w
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17712
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 and wishes so, or if the fe
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17931
> by still sending accumulator name for SQLMetrics
Do you have an idea of how much this undoes the benefits of SPARK-12837?
You're still avoiding sending the names of internal metrics, but I
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/17925#discussion_r116040106
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1054,15 +1053,17 @@ class DAGScheduler(
return
}
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17858#discussion_r116039639
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/InsertIntoHiveTableSuite.scala
---
@@ -494,4 +494,34 @@ class InsertIntoHiveTableSuite exten
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16989
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16989
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76812/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16648
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76818/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16648
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16648
**[Test build #76818 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76818/testReport)**
for PR 16648 at commit
[`f35ef24`](https://github.com/apache/spark/commit/f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16989
**[Test build #76812 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76812/testReport)**
for PR 16989 at commit
[`5ad4c3e`](https://github.com/apache/spark/commit/5
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17917
**[Test build #76817 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76817/testReport)**
for PR 17917 at commit
[`1a0e49e`](https://github.com/apache/spark/commit/1a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16648
**[Test build #76818 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76818/testReport)**
for PR 16648 at commit
[`f35ef24`](https://github.com/apache/spark/commit/f3
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/12313
We were trying to get this in just before the 2.0 release, which was a bad
time. We've just been maintaining it in our version, but I'm going to be
rebasing it on to 2.1 soon so I'll see what needs t
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/17917
https://cloud.githubusercontent.com/assets/62313/25960541/879096ce-3677-11e7-900f-09bd5f200a00.png";>
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16677
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76809/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16677
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
e
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/13206
@HyukjinKwon, that addresses part of what this patch does, but only for
writes that go through FileFormatWriter. This patch works for Hive and adds an
optimizer rule to add the sort instead of sortin
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16677
**[Test build #76809 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76809/testReport)**
for PR 16677 at commit
[`867a93d`](https://github.com/apache/spark/commit/8
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15652
I added this with #16625, this PR is not needed anymore. Please close.
---
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 issue:
https://github.com/apache/spark/pull/16648
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16648
**[Test build #76816 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76816/testReport)**
for PR 16648 at commit
[`f5f8f5c`](https://github.com/apache/spark/commit/f
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16648
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76816/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16648
**[Test build #76816 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76816/testReport)**
for PR 16648 at commit
[`f5f8f5c`](https://github.com/apache/spark/commit/f5
Github user zero323 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17938#discussion_r116030963
--- Diff: docs/sql-programming-guide.md ---
@@ -581,6 +581,46 @@ Starting from Spark 2.1, persistent datasource tables
have per-partition metadat
Github user zero323 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17938#discussion_r116029940
--- Diff: docs/sql-programming-guide.md ---
@@ -581,6 +581,46 @@ Starting from Spark 2.1, persistent datasource tables
have per-partition metadat
Github user devaraj-kavali closed the pull request at:
https://github.com/apache/spark/pull/16705
---
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 featur
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15049
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76811/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15049
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15049
**[Test build #76811 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76811/testReport)**
for PR 15049 at commit
[`f9b454b`](https://github.com/apache/spark/commit/f
Github user nblintao commented on the issue:
https://github.com/apache/spark/pull/14461
@HyukjinKwon Thanks for reminding. I am finals this week. I will fix this
after 15th.
---
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 nblintao commented on the issue:
https://github.com/apache/spark/pull/14158
@HyukjinKwon Thanks for reminding. I am finals this week. I will fix this
after 15th.
---
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 fjh100456 commented on the issue:
https://github.com/apache/spark/pull/17923
Well, I'll change the succeeded tasks of the all jobs page to the same as
the job detail page, and also record the completed tskid by a
"completedIndices".
Is it ok?
---
If your project is s
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16989
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16989
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76808/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16989
**[Test build #76808 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76808/testReport)**
for PR 16989 at commit
[`778c59b`](https://github.com/apache/spark/commit/7
Github user chie8842 commented on the issue:
https://github.com/apache/spark/pull/15652
@HyukjinKwon I'm sorry, I haven't reply for a long time.
I'll check it.
---
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 p
Github user mdespriee commented on the issue:
https://github.com/apache/spark/pull/17461
Yes, still active. I've been very busy lately.
Regarding 1/ -> will do
2/ -> still waiting for a comment from @jkbradley actually.
3/ -> will do
I'll try to move on in the
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/17945#discussion_r116018439
--- Diff: R/pkg/inst/tests/testthat/jarTest.R ---
@@ -16,7 +16,7 @@
#
library(SparkR)
-sc <- sparkR.session()
+sc <- sparkR.session(
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17952
Also, not really a big deal but probably, it would be nicer if this branch
`SPARK-20705` is rebased and synced to the master so that it only has few (or
single) commits. It looks a bit messy.
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17952
I am not used to UI code path but just while I am here I think this PR
should explain why it happens and how the current change fixes it. I am willing
to help reproduce this.
---
If your proje
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17402
I see. Thank you for your input.
---
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
enable
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17644
**[Test build #76815 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76815/testReport)**
for PR 17644 at commit
[`d01c721`](https://github.com/apache/spark/commit/d0
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17887
**[Test build #76814 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76814/testReport)**
for PR 17887 at commit
[`8ecb2ea`](https://github.com/apache/spark/commit/8e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17558
gentle ping @wangyum, is there any opinion on ^ ?
---
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 th
Github user jsoltren commented on the issue:
https://github.com/apache/spark/pull/17402
I'm still waiting on feedback from @joshrosen on my earlier question. I can
update this patch in response to @vanzin's review feedback if it would help to
get this checked in.
IMO this is
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/17644#discussion_r116012486
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -871,6 +886,23 @@ private[hive] object HiveClientImpl {
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17461
@mdespriee is it still active? Could you address the comment above?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17402
Hi @jsoltren, is this still active?
---
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
ena
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17938
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76813/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17938
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17938
**[Test build #76813 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76813/testReport)**
for PR 17938 at commit
[`a14296a`](https://github.com/apache/spark/commit/a
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17272
@windpiger is this still active?
---
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
enable
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17119
ping @windpiger is this still active?
---
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
e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17096
Hey @holdenk. I am willing to close this for now if you are not confident
enough for merging it for now. I can re-open this later.
---
If your project is set up for it, you can reply to this em
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17088
gentle ping @sitalkedia
---
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 wi
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17712
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17712
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76807/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17938
**[Test build #76813 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76813/testReport)**
for PR 17938 at commit
[`a14296a`](https://github.com/apache/spark/commit/a1
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17084
gentle ping @actuaryzhang
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17712
**[Test build #76807 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76807/testReport)**
for PR 17712 at commit
[`61bd96c`](https://github.com/apache/spark/commit/6
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17052
@uncleGen is this still active?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17006
@ndimiduk Let's close this for now if it is going to be inactive. I am not
sure of the current way due to the test failure and we can continue to discuss
this in the JIRA. If you think the JIRA
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17001
any update? ping @windpiger
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16975
Hi @andrewor14, is this still active?
---
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
e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16912
Hi @sharkdtu, is there any opinion on ^? If it is inactive, I would rather
like to propose to close this.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16893
Hi all, where are we on this? Is this still active?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16812
Hm, do we really need this? I think we could simply work around this by
`case` & `when`, `if` or other expressions with a projection after loading. Or
using `csv(ds: Dataset[String])` API after
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/17644#discussion_r116003799
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/ExternalCatalog.scala
---
@@ -335,6 +336,32 @@ abstract class ExternalCatal
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/17644#discussion_r116003794
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -902,9 +902,14 @@ case class ShowCreateTableCommand(table:
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16743
Hi @thomastechs, is it still active and any opinion on ^ ? Otherwise, I
would like to propose to close this.
---
If your project is set up for it, you can reply to this email and have your
repl
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16648
Yea, I just wanted to make sure this is on progress in any way.
---
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 do
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16697
@CodingCat is this still active and any opinion on ^?
---
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 bdrillard commented on the issue:
https://github.com/apache/spark/pull/16648
@HyukjinKwon @robert3005 I'll have some time soon to update this PR for the
latest master. Thanks for the interest. It is a non-trivial change and would
require a comprehensive code review.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16654
gentle ping @zhengruifeng
---
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 w
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16652
gentle ping @admackin
---
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 wish
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16648
gentle ping @bdrillard
---
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 wish
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16611
gentle ping ...
---
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,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16598
Hi @arman1371, is it still active?
---
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
enab
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/14702
I dont see I will be getting time to work on this. Will close the PR for
now and revisit in future.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user tejasapatil closed the pull request at:
https://github.com/apache/spark/pull/14702
---
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 i
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16389
@zhaorongsheng, is this still active and any opinion on ^?
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/16705
@devaraj-kavali thanks, it looks like this is already fixed in spark 2.2
with SPARK-20217 please close.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16291
what's the current status of 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 this feature
e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16285
Hi @jojochuang, is it still active? If so, I think we should address this
comment ^.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16199
@NathanHowell, please let me know. I can pick up the commits and take over.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15918
Hi @windpiger, is this still WIP?
---
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
enabl
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15914
Hi @baishuo, how could this be manually tested? I would like to verify this
case.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15850
Hi @gatorsmile, is this still WIP?
---
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
enab
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15831
Hi @@techaddict, how is this PR going?
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/17887#discussion_r115995239
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/regexpExpressions.scala
---
@@ -144,7 +151,31 @@ case class Like(left: Expre
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/17935
cc @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 wishes so, or if
301 - 400 of 630 matches
Mail list logo
