Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13156#issuecomment-219918792
**[Test build #58740 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58740/consoleFull)**
for PR 13156 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13161#issuecomment-219920955
**[Test build #58735 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58735/consoleFull)**
for PR 13161 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219922177
**[Test build #58742 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58742/consoleFull)**
for PR 13129 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13161#issuecomment-21990
**[Test build #58736 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58736/consoleFull)**
for PR 13161 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13102#issuecomment-219927672
Sorry this is not what I meant in the JIRA ticket. What I meant was that we
should just save SparkSessions, and then SQLContext calls into that. I didn't
mean to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13101#issuecomment-219915297
**[Test build #58737 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58737/consoleFull)**
for PR 13101 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13162#issuecomment-219922548
**[Test build #58738 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58738/consoleFull)**
for PR 13162 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13162#issuecomment-219922682
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/13162#issuecomment-219922683
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/13129#issuecomment-219928428
**[Test build #58744 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58744/consoleFull)**
for PR 13129 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219928499
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13156#discussion_r63646713
--- Diff:
sql/hivecontext-compatibility/src/test/scala/org/apache/spark/sql/hive/HiveContextCompatibilitySuite.scala
---
@@ -99,4 +105,41 @@ class
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/13156#discussion_r63647706
--- Diff:
sql/hivecontext-compatibility/src/test/scala/org/apache/spark/sql/hive/HiveContextCompatibilitySuite.scala
---
@@ -99,4 +105,41 @@ class
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/13156#discussion_r63643173
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/MetastoreDataSourcesSuite.scala
---
@@ -622,7 +622,7 @@ class MetastoreDataSourcesSuite extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13101#issuecomment-219915352
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/13101#issuecomment-219915350
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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13135#discussion_r63640828
--- Diff: examples/src/main/python/ml/simple_params_example.py ---
@@ -36,18 +35,20 @@
if len(sys.argv) > 1:
--- End diff --
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13135#discussion_r63640687
--- Diff: examples/src/main/python/ml/simple_params_example.py ---
@@ -36,18 +35,20 @@
if len(sys.argv) > 1:
--- End diff --
I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13127#issuecomment-219918389
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/13127#issuecomment-219918386
**[Test build #58739 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58739/consoleFull)**
for PR 13127 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13127#issuecomment-219918225
**[Test build #58739 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58739/consoleFull)**
for PR 13127 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13127#issuecomment-219918387
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13161#issuecomment-219921049
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/13161#issuecomment-219921050
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/13156#discussion_r63644169
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/MetastoreDataSourcesSuite.scala
---
@@ -622,7 +622,7 @@ class MetastoreDataSourcesSuite
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219924209
**[Test build #58744 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58744/consoleFull)**
for PR 13129 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13135#discussion_r63644923
--- Diff: examples/src/main/python/ml/simple_params_example.py ---
@@ -36,18 +35,20 @@
if len(sys.argv) > 1:
--- End diff --
Thank
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219928497
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12979#issuecomment-219930465
**[Test build #58746 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58746/consoleFull)**
for PR 12979 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13156#issuecomment-219931477
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/12939#issuecomment-219931480
Lots of punctuation characters like `*`, `+` can be used as an operator in
expressions so I'm afraid comments in generated code will be difficult to read
if characters
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/13158#issuecomment-219931535
cc @andrewor14 @zsxwing
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/13160#issuecomment-219911211
logging a warning seems like a good idea!
---
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 zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13135#discussion_r63638222
--- Diff: examples/src/main/python/ml/simple_params_example.py ---
@@ -36,18 +35,20 @@
if len(sys.argv) > 1:
--- End diff --
It
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13101#issuecomment-219910742
**[Test build #58737 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58737/consoleFull)**
for PR 13101 at commit
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/13160#issuecomment-219910757
Changing sql conf setting seems a better approach. Besides that some other
setting in SparkSession#Build also won't take effect if there's already an
existing
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13161#issuecomment-219910188
(@ericl I see you set a component in JIRA. It would be nicer if the
component is specified in the PR title as described in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13161#issuecomment-219910107
**[Test build #58736 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58736/consoleFull)**
for PR 13161 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13135#discussion_r63638465
--- Diff: examples/src/main/python/ml/simple_params_example.py ---
@@ -36,18 +35,20 @@
if len(sys.argv) > 1:
--- End diff --
Hm..
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13129#discussion_r63643069
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -252,7 +250,7 @@ class LinearRegression @Since("1.3.0")
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/13135#discussion_r63643565
--- Diff: examples/src/main/python/ml/simple_params_example.py ---
@@ -36,18 +35,20 @@
if len(sys.argv) > 1:
--- End diff --
We're
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13161#issuecomment-219922326
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/13161#issuecomment-219922327
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/13135#issuecomment-219926751
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/13135#issuecomment-219926703
**[Test build #58745 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58745/consoleFull)**
for PR 13135 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13135#issuecomment-219926748
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13148#issuecomment-219927902
**[Test build #58743 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58743/consoleFull)**
for PR 13148 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13148#issuecomment-219927963
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/13148#issuecomment-219927964
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12979#issuecomment-219932274
@sarutak It's expected to compile twice on two different queries, it does
not worth to optimize this corner case (ideally it should generate different
source code even
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219926099
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/13129#issuecomment-219926097
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/12939#issuecomment-219931861
We can just expand the whitelist and add * + and such into that can't we?
My main worry is that security is very difficult to get right, and having a
whitelist
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/13161#discussion_r63637597
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/SortOrder.scala
---
@@ -64,49 +64,57 @@ case class SortOrder(child:
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/7025#discussion_r63638336
--- Diff: R/pkg/R/client.R ---
@@ -42,6 +42,19 @@ determineSparkSubmitBin <- function() {
}
sparkSubmitBinName
}
+# R supports both
Github user zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13135#discussion_r63638842
--- Diff: examples/src/main/python/ml/simple_params_example.py ---
@@ -36,18 +35,20 @@
if len(sys.argv) > 1:
--- End diff --
This
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13162#issuecomment-219914340
**[Test build #58738 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58738/consoleFull)**
for PR 13162 at commit
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/13162
[SPARK-15375][SQL][Streaming] Add ConsoleSink to structure streaming
## What changes were proposed in this pull request?
Add ConsoleSink to structure streaming, user could use it to
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/13135#issuecomment-219922114
@HyukjinKwon ah right, of course. I forgot the params get set during `fit`
in Python.
---
If your project is set up for it, you can reply to this email and have your
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/12836#issuecomment-219925061
I mean is it too simple to allow grouping by columns only - what if after
grouped by columns the dataset is too large to fit in memory?
What if we are to
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/13134#issuecomment-219914749
cc @davies Please take a look, 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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219920209
**[Test build #58741 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58741/consoleFull)**
for PR 13008 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13135#issuecomment-219925856
**[Test build #58745 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58745/consoleFull)**
for PR 13135 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219926031
**[Test build #58742 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58742/consoleFull)**
for PR 13129 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219929253
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219929255
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/13138#issuecomment-219640717
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/13138#issuecomment-219640714
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/13129#issuecomment-219646339
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219646199
**[Test build #58673 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58673/consoleFull)**
for PR 13129 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219646342
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/13142#issuecomment-219650730
**[Test build #58672 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58672/consoleFull)**
for PR 13142 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13074#issuecomment-219658693
Merged to master/2.0
---
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 dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/13145
[MINOR][SQL] Remove unused pattern matching variables in Optimizers.
## What changes were proposed in this pull request?
This PR removes unused pattern matching variable in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219669778
**[Test build #58678 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58678/consoleFull)**
for PR 13008 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219669830
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/13008#issuecomment-219669826
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/13147#issuecomment-219673646
**[Test build #58683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58683/consoleFull)**
for PR 13147 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219675846
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/13144#issuecomment-219676184
**[Test build #58677 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58677/consoleFull)**
for PR 13144 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13129#discussion_r63474760
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -239,10 +239,7 @@ class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13095#issuecomment-219639437
**[Test build #58667 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58667/consoleFull)**
for PR 13095 at commit
Github user viirya closed the pull request at:
https://github.com/apache/spark/pull/12870
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/13042#issuecomment-219659234
I'm OK with just the first change, for tidiness.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219662340
**[Test build #58680 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58680/consoleFull)**
for PR 13008 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219662330
**[Test build #58679 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58679/consoleFull)**
for PR 13145 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219664628
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/13008#issuecomment-219664603
**[Test build #58680 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58680/consoleFull)**
for PR 13008 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219664629
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/12627#issuecomment-219673118
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/12627#issuecomment-219672925
**[Test build #58674 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58674/consoleFull)**
for PR 12627 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13145#discussion_r63496130
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -440,10 +439,10 @@ object ColumnPruning extends
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219677538
Looks reasonable, but I wonder if this should be done at once for all of
the code base?
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219635956
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13138#issuecomment-219640461
**[Test build #58669 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58669/consoleFull)**
for PR 13138 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13142#issuecomment-219650975
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-219651320
**[Test build #58676 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58676/consoleFull)**
for PR 12257 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13142#issuecomment-219650978
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/13144
[SPARK-14346][SQL][follow-up] add tests for CREAT TABLE USING with
partition and bucket
## What changes were proposed in this pull request?
https://github.com/apache/spark/pull/12781
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/13045#issuecomment-219670131
I don't have a good idea either, one possible approach is improving
`UnresolvedAlias` to take a function as the optional alias name, and the
function will take the
1 - 100 of 586 matches
Mail list logo
