Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6508#issuecomment-109644093
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/6508#issuecomment-109644090
[Test build #34376 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34376/console)
for PR 6508 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r31871274
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/DataType.scala ---
@@ -376,4 +376,26 @@ object DataType {
case (fromDataType,
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r31871270
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/DataType.scala ---
@@ -376,4 +376,26 @@ object DataType {
case (fromDataType,
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r31871263
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/DataType.scala ---
@@ -376,4 +376,26 @@ object DataType {
case (fromDataType,
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r31871281
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/StructType.scala ---
@@ -104,6 +104,34 @@ case class StructType(fields: Array[StructField])
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r31871289
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/StructType.scala ---
@@ -104,6 +104,34 @@ case class StructType(fields: Array[StructField])
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r31871291
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/DataType.scala ---
@@ -376,4 +376,26 @@ object DataType {
case (fromDataType,
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6680#discussion_r31871330
--- Diff:
yarn/src/test/scala/org/apache/spark/deploy/yarn/YarnClusterSuite.scala ---
@@ -351,11 +352,13 @@ private object YarnClusterDriver extends
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6675#issuecomment-109536347
We would add these capabilities for 1.5, but do you mind we holding off
merging this PR? It'd be good for us to design this more holistically before
merging explicit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109548407
[Test build #34358 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34358/console)
for PR 6660 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6660#discussion_r31865673
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -33,21 +32,167 @@ class IntegerHashSet
Github user yijieshen commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-109544645
@rxin, can you help me to review the latest commit?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6669#issuecomment-109546732
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/6660#issuecomment-109546733
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/6660#issuecomment-109546757
[Test build #34357 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34357/consoleFull)
for PR 6660 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6681#issuecomment-109546754
[Test build #34356 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34356/consoleFull)
for PR 6681 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109546731
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/6670#issuecomment-109546730
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/6681#issuecomment-109546729
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/5921#issuecomment-109553180
@tdas are you OK with this change?
---
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/6681#issuecomment-109534638
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 dongwang218 commented on the pull request:
https://github.com/apache/spark/pull/6681#issuecomment-109534579
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
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6660#discussion_r31865645
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/Expression.scala
---
@@ -52,6 +53,45 @@ abstract class Expression extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109548419
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6680#discussion_r31866108
--- Diff:
yarn/src/test/scala/org/apache/spark/deploy/yarn/YarnClusterSuite.scala ---
@@ -351,11 +352,13 @@ private object YarnClusterDriver extends Logging
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6678#issuecomment-109534701
If it is immutable, there isn't anything to expand right?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109545293
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/6660#issuecomment-109547097
[Test build #34358 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34358/consoleFull)
for PR 6660 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6610#issuecomment-109534820
Filed SPARK-8138 for this and updated PR title.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109543714
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/6669#issuecomment-109546805
[Test build #34355 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34355/consoleFull)
for PR 6669 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109546799
[Test build #34357 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34357/console)
for PR 6660 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6670#issuecomment-109546809
[Test build #34354 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34354/consoleFull)
for PR 6670 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109546803
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6492#issuecomment-109553915
I'm inclined to pull this in if in fact it works with Scala 2.11 this time
around, as reported on the JIRA. 2.3.11 is claimed to be a drop in replacement
for earlier
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6612#issuecomment-109555381
@yhuai Added summary [in the JIRA ticket] [1]. I'm merging this to master
and branch-1.4.
[1]:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6265#issuecomment-109561128
[Test build #34359 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34359/consoleFull)
for PR 6265 at commit
GitHub user jeanlyn opened a pull request:
https://github.com/apache/spark/pull/6682
[SPARK-2205][SPARK-7871][SQL]Advoid redundancy exchange
When only use the output partitioning of `BinaryNode` will probably add
unnecessary `Exchange` like multiway join.
This PR add
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6265#issuecomment-109570501
[Test build #34359 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34359/console)
for PR 6265 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6265#issuecomment-109570502
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 MechCoder opened a pull request:
https://github.com/apache/spark/pull/6684
[SPARK-8140] [MLlib] Minor internal improvements in Streaming MLlib
Algorithms
1. Prevent creating a map of data to find numFeatures
2. If model is empty, then initialize with a zero vector
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6684#discussion_r31868153
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/GeneralizedLinearAlgorithm.scala
---
@@ -195,11 +195,11 @@ abstract class
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6684#discussion_r31868157
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/StreamingLinearAlgorithm.scala
---
@@ -79,9 +79,6 @@ abstract class
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/6684#discussion_r31868166
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/GeneralizedLinearAlgorithm.scala
---
@@ -195,11 +195,11 @@ abstract class
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-109557409
@Sephiroth-Lin does it hurt to cleanup on KILLED in ApplicationMaster
though? we're trying to make more effort to clean up in this case.
---
If your project is set up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6265#issuecomment-109560795
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/6265#issuecomment-109560782
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 jeanlyn commented on the pull request:
https://github.com/apache/spark/pull/6682#issuecomment-109564743
cc @yhuai @chenghao-intel
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6684#issuecomment-109580561
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/6684#issuecomment-109580554
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/6684#issuecomment-109580979
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/6684#issuecomment-109580985
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6674#issuecomment-109555446
Looks good to me. Do we need any additional testing before trying to merge
it again? I could merge to master and then later backport if it seems OK for a
few days.
---
Github user liancheng closed the pull request at:
https://github.com/apache/spark/pull/6612
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/6612#issuecomment-109562405
Seems that the merge script failed to close this PR. Closing it manually.
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/6683
[SPARK-8139] [SQL] Updates docs and comments of data sources and Parquet
output committr options
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6682#issuecomment-109564823
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/6683#issuecomment-109565173
[Test build #34360 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34360/consoleFull)
for PR 6683 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6683#issuecomment-109565056
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/6684#issuecomment-109580388
[Test build #34361 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34361/consoleFull)
for PR 6684 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6684#issuecomment-109580370
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/6684#issuecomment-109580363
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/6684#issuecomment-109580631
[Test build #34362 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34362/consoleFull)
for PR 6684 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6684#issuecomment-109580993
[Test build #34363 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34363/consoleFull)
for PR 6684 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6669#issuecomment-109557941
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/6681#issuecomment-109561495
[Test build #34356 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34356/consoleFull)
for PR 6681 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6681#issuecomment-109561504
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/6683#issuecomment-109565049
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/6683#issuecomment-109579600
[Test build #34360 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34360/console)
for PR 6683 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6683#issuecomment-109579631
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/6670#issuecomment-109557918
[Test build #34354 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34354/console)
for PR 6670 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6669#issuecomment-109557937
[Test build #34355 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34355/console)
for PR 6669 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6670#issuecomment-109557925
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/6683#discussion_r31867107
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLConf.scala ---
@@ -43,9 +43,19 @@ private[spark] object SQLConf {
val
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6684#discussion_r31868146
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/GeneralizedLinearAlgorithm.scala
---
@@ -179,7 +179,7 @@ abstract class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6684#issuecomment-109602949
[Test build #34362 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34362/console)
for PR 6684 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6684#issuecomment-109602976
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 shijinkui opened a pull request:
https://github.com/apache/spark/pull/6685
[SPARK-7893][Graphx]Complex Operators between Graphs: Union
Union of Graphs ( G ⪠H )
You can merge this pull request into a Git repository by running:
$ git pull
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/6653#issuecomment-109605849
@vanzin @srowen this broke the Spark 1.3 builds, so I revert it in the
Spark 1.3 branch.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-109607261
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/6684#issuecomment-109607304
[Test build #34369 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34369/consoleFull)
for PR 6684 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-109607259
[Test build #34368 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34368/console)
for PR 6686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6687#issuecomment-109617342
[Test build #34372 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34372/consoleFull)
for PR 6687 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-109617492
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/6686#issuecomment-109617547
[Test build #34373 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34373/consoleFull)
for PR 6686 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/6645#issuecomment-109618837
In `HiveTypeCoercion`, there is a `StringToIntegralCasts` which casts a
string to an integral type. When the string represents a fractional number, jvm
will throw a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6684#issuecomment-109582135
[Test build #34364 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34364/consoleFull)
for PR 6684 at commit
Github user hqzizania closed the pull request at:
https://github.com/apache/spark/pull/6190
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/6684#discussion_r31868395
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/StreamingLinearAlgorithm.scala
---
@@ -79,9 +79,6 @@ abstract class
Github user koeninger commented on a diff in the pull request:
https://github.com/apache/spark/pull/6632#discussion_r31868393
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaRDD.scala
---
@@ -60,6 +62,49 @@ class KafkaRDD[
}.toArray
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-109586761
[Test build #34365 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34365/consoleFull)
for PR 6672 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6457#issuecomment-109590433
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/6457#issuecomment-109590358
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/6685#issuecomment-109606270
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6684#issuecomment-109606963
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 ilganeli opened a pull request:
https://github.com/apache/spark/pull/6686
[SPARK-8056][SQL][WIP] Design an easier way to construct schema for both
Scala and Python
I've added functionality to create new StructType similar to how we add
parameters to a new SparkContext.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-109606945
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/6686#issuecomment-109606962
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/6684#issuecomment-109606950
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
1 - 100 of 245 matches
Mail list logo
