Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8189
---
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 yanboliang opened a pull request:
https://github.com/apache/spark/pull/8225
[SPARK-10029] [MLlib] [Doc] Add Python examples for mllib
IsotonicRegression user guide
Add Python examples for mllib IsotonicRegression user guide
You can merge this pull request into a Git
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8189#issuecomment-131497925
This is fine for 1.5.
---
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 yjshen opened a pull request:
https://github.com/apache/spark/pull/8224
[SPARK-9431][SQL]TimeIntervalType for for time intervals
TimeIntervalType is stored as Long internally, represents the number of
microseconds and can be used in equality tests and ordering.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8224#issuecomment-131504435
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/8224#issuecomment-131504431
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/8189#issuecomment-131496028
@viper-kun Please add your name and email address to GitHub so that we can
include that information while merging your PRs. I've added you information
gathered from
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7419#issuecomment-131496645
LGTM. Merging this
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6848#issuecomment-131496679
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/6848#issuecomment-131496680
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/8224#issuecomment-131504609
[Test build #40985 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40985/consoleFull)
for PR 8224 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8225#issuecomment-131507372
[Test build #40986 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40986/consoleFull)
for PR 8225 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6848#issuecomment-131496471
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/6848#issuecomment-131496469
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8220
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/7419
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8225#issuecomment-131505931
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/8225#issuecomment-131505895
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/8226#issuecomment-131543038
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 sryza opened a pull request:
https://github.com/apache/spark/pull/8230
SPARK-7707. User guide and example code for KernelDensity
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sryza/spark sandy-spark-7707
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8230#issuecomment-131548628
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/8230#issuecomment-131548680
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/8230#issuecomment-131549632
[Test build #40995 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40995/consoleFull)
for PR 8230 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8230#issuecomment-131552714
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/8230#issuecomment-131552681
[Test build #40995 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40995/console)
for PR 8230 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8230#issuecomment-131552713
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/8224#issuecomment-131530484
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/8224#issuecomment-131530481
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/8224#issuecomment-131530374
[Test build #40985 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40985/console)
for PR 8224 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8227#issuecomment-131530708
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/8224#issuecomment-131530705
[Test build #40992 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40992/consoleFull)
for PR 8224 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8227#issuecomment-131530706
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/8226#issuecomment-131531022
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/8226#issuecomment-131531024
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/8226#issuecomment-131530947
[Test build #40987 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40987/console)
for PR 8226 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8230#issuecomment-131546131
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/8230#issuecomment-131546133
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/8228#issuecomment-131529908
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/8228#issuecomment-131529913
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/8227#issuecomment-131530691
[Test build #40990 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40990/console)
for PR 8227 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8224#issuecomment-131530649
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/8224#issuecomment-131530655
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/8226#issuecomment-131519388
[Test build #40987 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40987/consoleFull)
for PR 8226 at commit
Github user BertrandDechoux commented on the pull request:
https://github.com/apache/spark/pull/8062#issuecomment-131519310
It's all good.
---
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/8225#issuecomment-131511468
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/8225#issuecomment-131511472
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/8225#issuecomment-131511126
[Test build #40986 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40986/console)
for PR 8225 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8226#issuecomment-131518067
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8226#discussion_r37144278
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/SortMergeJoin.scala
---
@@ -96,9 +103,37 @@ case class SortMergeJoin(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8226#issuecomment-131518030
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/8226#issuecomment-131545027
[Test build #40994 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40994/consoleFull)
for PR 8226 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/8228
[SPARK-10005] [SQL] Fixes schema merging for nested structs
In case of schema merging, we only handled first level fields when
converting Parquet groups to `InternalRow`s. Nested struct fields
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8227#issuecomment-131529773
[Test build #40990 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40990/consoleFull)
for PR 8227 at commit
GitHub user XiaoqingWang opened a pull request:
https://github.com/apache/spark/pull/8229
SPARK-8918 Add @since tags to mllib.clustering
I am so sorry for the delay.
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/8226#issuecomment-131543564
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/8226#issuecomment-131543496
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/8230#issuecomment-131543487
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/8230#issuecomment-131543538
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 sryza commented on the pull request:
https://github.com/apache/spark/pull/8071#issuecomment-131547053
Sorry all for the delay, have been in Indonesia for the week.
I'm also in favor of the standard way being --deploy-mode. This keeps
things consistent with
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/8230#issuecomment-131547427
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 viirya opened a pull request:
https://github.com/apache/spark/pull/8226
[SPARK-10031][SQL] Join two UnsafeRows in SortMergeJoin if possible
JIRA: https://issues.apache.org/jira/browse/SPARK-10031
Currently in `SortMergeJoin`, when two rows from left and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8197#issuecomment-131523642
[Test build #40988 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40988/consoleFull)
for PR 8197 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8197#issuecomment-131523608
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/8197#issuecomment-131523605
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/8197#issuecomment-131525240
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/8197#issuecomment-131525225
[Test build #40988 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40988/console)
for PR 8197 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8197#issuecomment-131525241
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/8227
[SPARK-10032] [PySpark] [Doc] Add Python example for mllib LDAModel user
guide
Add Python example for mllib LDAModel user guide
You can merge this pull request into a Git repository by running:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8227#issuecomment-131528736
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/8227#issuecomment-131528767
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/8228#issuecomment-131529752
cc @yhuai
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8228#issuecomment-131530038
[Test build #40991 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40991/consoleFull)
for PR 8228 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8229#issuecomment-131534015
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 XiaoqingWang commented on the pull request:
https://github.com/apache/spark/pull/7662#issuecomment-131535501
a new pull request (apache/spark#8229) for this has been submited,I am
sorry for the delay,please help to review ,thanks
---
If your project is set up for it, you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8226#issuecomment-131569632
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8228#issuecomment-131584183
LGTM. Merging to master and branch 1.5. Let's also take a look at cases
when catalyst schema is a subset of parquet schema (it may happen when users
provide schema of the
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8191#issuecomment-131598385
@marmbrus Had some offline discussions with @yhuai, and we believe that the
real problem we hit in the job behind SPARK-9899 is SPARK-10005 (fixed by
#8228).
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8228#discussion_r37148466
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/CatalystRowConverter.scala
---
@@ -126,7 +169,24 @@ private[parquet]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8228#issuecomment-131553936
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/8231#issuecomment-131568826
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/8232#issuecomment-131575753
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8228#discussion_r37147548
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/CatalystRowConverter.scala
---
@@ -126,7 +169,24 @@ private[parquet]
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8228#discussion_r37147799
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/CatalystSchemaConverter.scala
---
@@ -72,18 +72,9 @@ private[parquet]
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8228#discussion_r37147999
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/CatalystRowConverter.scala
---
@@ -126,7 +169,24 @@ private[parquet]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8232#issuecomment-131598249
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/8226#issuecomment-131569631
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/8231#issuecomment-131569603
[Test build #40996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40996/consoleFull)
for PR 8231 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8226#issuecomment-131569602
[Test build #40994 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40994/console)
for PR 8226 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8232#issuecomment-131575905
DataFrameReader.jdbc and DataFrameWriter.jdbc ignore `extraOptions`
currently. Is it intentional, or a bug?
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8224#issuecomment-131560395
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/8224#issuecomment-131560401
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/8224#issuecomment-131560094
[Test build #40992 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40992/console)
for PR 8224 at commit
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/8232
[SPARK-10036][SQL]Load JDBC driver in DataFrameReader.jdbc and
DataFrameWriter.jdbc
This PR uses `JDBCRDD.getConnector` to load JDBC driver before creating
connection in `DataFrameReader.jdbc` and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8232#issuecomment-131576151
[Test build #40997 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40997/consoleFull)
for PR 8232 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8228
---
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8231#issuecomment-131567664
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/8231
[SPARK-10034][SQL] Can't analyze Sort on Aggregate with aggregation
expression named _aggOrdering
The reason of this bug is that: The aggregate expression in `SortOrder`
never get resolved, we
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8232#issuecomment-131575756
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/8231#issuecomment-131584043
[Test build #40996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40996/console)
for PR 8231 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8231#issuecomment-131584080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 209 matches
Mail list logo
