[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17316 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

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17316 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74672/ Test PASSed. ---

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17316 **[Test build #74672 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74672/testReport)** for PR 17316 at commit

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17316 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74669/ Test PASSed. ---

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17316 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

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17316 **[Test build #74669 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74669/testReport)** for PR 17316 at commit

[GitHub] spark issue #17317: [SPARK-19329][SQL][BRANCH-2.1]Reading from or writing to...

Github user windpiger commented on the issue: https://github.com/apache/spark/pull/17317 cc @gatorsmile --- 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] spark issue #16618: [SPARK-14409][ML][WIP] Add RankingEvaluator

Github user MLnick commented on the issue: https://github.com/apache/spark/pull/16618 The basic direction looks right - I won't have time to review immediately. Spark 2.2 QA code freeze will happen shortly so this will wait until 2.3 dev cycle starts --- If your project is set up

[GitHub] spark issue #16867: [SPARK-16929] Improve performance when check speculatabl...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16867 **[Test build #74673 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74673/testReport)** for PR 16867 at commit

[GitHub] spark pull request #16867: [SPARK-16929] Improve performance when check spec...

Github user squito commented on a diff in the pull request: https://github.com/apache/spark/pull/16867#discussion_r106433116 --- Diff: core/src/test/scala/org/apache/spark/util/collection/MedianHeapSuite.scala --- @@ -0,0 +1,67 @@ +/* + * Licensed to the Apache Software

[GitHub] spark pull request #16867: [SPARK-16929] Improve performance when check spec...

Github user squito commented on a diff in the pull request: https://github.com/apache/spark/pull/16867#discussion_r106436689 --- Diff: core/src/test/scala/org/apache/spark/util/collection/MedianHeapSuite.scala --- @@ -0,0 +1,67 @@ +/* + * Licensed to the Apache Software

[GitHub] spark pull request #16867: [SPARK-16929] Improve performance when check spec...

Github user squito commented on a diff in the pull request: https://github.com/apache/spark/pull/16867#discussion_r106434806 --- Diff: core/src/test/scala/org/apache/spark/util/collection/MedianHeapSuite.scala --- @@ -0,0 +1,67 @@ +/* + * Licensed to the Apache Software

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17316 **[Test build #74672 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74672/testReport)** for PR 17316 at commit

[GitHub] spark issue #17317: [SPARK-19329][SQL][BRANCH-2.1]Reading from or writing to...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17317 **[Test build #74671 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74671/testReport)** for PR 17317 at commit

[GitHub] spark pull request #17317: [SPARK-19329][SQL][BRANCH-2.1]Reading from or wri...

GitHub user windpiger opened a pull request: https://github.com/apache/spark/pull/17317 [SPARK-19329][SQL][BRANCH-2.1]Reading from or writing to a datasource table with a non pre-existing location should succeed ## What changes were proposed in this pull request? This is a

[GitHub] spark issue #17274: [SPARK-19925][SPARKR] Fix SparkR spark.getSparkFiles fai...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17274 **[Test build #74668 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74668/testReport)** for PR 17274 at commit

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17316 **[Test build #74669 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74669/testReport)** for PR 17316 at commit

[GitHub] spark issue #17242: [SPARK-19902][SQL] Add optimization rule to simplify exp...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17242 **[Test build #74670 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74670/testReport)** for PR 17242 at commit

[GitHub] spark pull request #16867: [SPARK-16929] Improve performance when check spec...

Github user jinxing64 commented on a diff in the pull request: https://github.com/apache/spark/pull/16867#discussion_r106433273 --- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala --- @@ -172,7 +172,7 @@ private[spark] class TaskSchedulerImpl

[GitHub] spark issue #17274: [SPARK-19925][SPARKR] Fix SparkR spark.getSparkFiles fai...

Github user yanboliang commented on the issue: https://github.com/apache/spark/pull/17274 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 have this feature enabled and

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17316 **[Test build #74667 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74667/testReport)** for PR 17316 at commit

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17316 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

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17316 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74667/ Test FAILed. ---

[GitHub] spark pull request #17292: [SPARK-19946][testing]DebugFilesystem.assertNoOpe...

Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/17292 --- 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] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17316 **[Test build #74667 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74667/testReport)** for PR 17316 at commit

[GitHub] spark issue #16483: [SPARK-18847][GraphX] PageRank gives incorrect results f...

Github user aray commented on the issue: https://github.com/apache/spark/pull/16483 @rxin can anyone else review this? It would be nice to get this correctness fix into 2.2. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] spark issue #17292: [SPARK-19946][testing]DebugFilesystem.assertNoOpenStream...

Github user hvanhovell commented on the issue: https://github.com/apache/spark/pull/17292 LGTM - merging to master. 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 does not have this feature

[GitHub] spark issue #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

Github user MLnick commented on the issue: https://github.com/apache/spark/pull/17316 cc @hhbyyh --- 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

[GitHub] spark pull request #17316: [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark

GitHub user MLnick opened a pull request: https://github.com/apache/spark/pull/17316 [SPARK-15040][ML][PYSPARK] Add Imputer to PySpark Add Python wrapper for `Imputer` feature transformer. ## How was this patch tested? New doc tests and tweak to PySpark ML

[GitHub] spark pull request #17315: [SPARK-19949][SQL] unify bad record handling in C...

GitHub user cloud-fan opened a pull request: https://github.com/apache/spark/pull/17315 [SPARK-19949][SQL] unify bad record handling in CSV and JSON ## What changes were proposed in this pull request? Currently JSON and CSV have exactly the same logic about handling bad

[GitHub] spark issue #17315: [SPARK-19949][SQL] unify bad record handling in CSV and ...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17315 **[Test build #74666 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74666/testReport)** for PR 17315 at commit

[GitHub] spark issue #17315: [SPARK-19949][SQL] unify bad record handling in CSV and ...

Github user cloud-fan commented on the issue: https://github.com/apache/spark/pull/17315 cc @sameeragarwal @HyukjinKwon --- 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] spark pull request #17291: [SPARK-19949][SQL][WIP] unify bad record handling...

Github user cloud-fan closed the pull request at: https://github.com/apache/spark/pull/17291 --- 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] spark pull request #16867: [SPARK-16929] Improve performance when check spec...

Github user squito commented on a diff in the pull request: https://github.com/apache/spark/pull/16867#discussion_r106421711 --- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala --- @@ -172,7 +172,7 @@ private[spark] class TaskSchedulerImpl

[GitHub] spark issue #17268: [SPARK-19932][SS] Disallow a case that might case OOM fo...

Github user lw-lin commented on the issue: https://github.com/apache/spark/pull/17268 Sure; sorry I didn't say it out but I meant the same thing :-) @marmbrus now that I've updated this as well as the JIRA, would you mind taking another look? Thanks! --- If your project is

[GitHub] spark issue #17238: getRackForHost returns None if host is unknown by driver

Github user tgravescs commented on the issue: https://github.com/apache/spark/pull/17238 > Actually, to play devil's advocate, the problem @morenn520 is describing is a little more involved. You have a driver running, which has its own view of what the cluster topology is, and then

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17312 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

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17312 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74663/ Test PASSed. ---

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17312 **[Test build #74663 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74663/testReport)** for PR 17312 at commit

[GitHub] spark issue #17276: [WIP][SPARK-19937] Collect metrics of block sizes when s...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17276 **[Test build #74665 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74665/testReport)** for PR 17276 at commit

[GitHub] spark issue #16330: [SPARK-18817][SPARKR][SQL] change derby log output to te...

Github user shivaram commented on the issue: https://github.com/apache/spark/pull/16330 Sounds good to me. On Mar 16, 2017 04:24, "Felix Cheung" wrote: > *@felixcheung* commented on this pull request. > --

[GitHub] spark issue #16596: [SPARK-19237][SPARKR][WIP] R should check for java when ...

Github user shivaram commented on the issue: https://github.com/apache/spark/pull/16596 I think echoing an error message earlier than 1 minute would be useful. What would be the files we'd need to change for that ? --- If your project is set up for it, you can reply to this email

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17312 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

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17312 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74662/ Test PASSed. ---

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17312 **[Test build #74662 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74662/testReport)** for PR 17312 at commit

[GitHub] spark issue #16672: [SPARK-19329][SQL]Reading from or writing to a datasourc...

Github user windpiger commented on the issue: https://github.com/apache/spark/pull/16672 ok thanks，its my pleasure～ --- 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] spark issue #17311: [SPARK-19970][SQL] Table owner should be USER instead of...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17311 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

[GitHub] spark issue #17311: [SPARK-19970][SQL] Table owner should be USER instead of...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17311 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74664/ Test PASSed. ---

[GitHub] spark issue #17311: [SPARK-19970][SQL] Table owner should be USER instead of...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17311 **[Test build #74664 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74664/testReport)** for PR 17311 at commit

[GitHub] spark issue #17292: [SPARK-19946][testing]DebugFilesystem.assertNoOpenStream...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17292 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74659/ Test PASSed. ---

[GitHub] spark issue #17292: [SPARK-19946][testing]DebugFilesystem.assertNoOpenStream...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17292 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

[GitHub] spark issue #17292: [SPARK-19946][testing]DebugFilesystem.assertNoOpenStream...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17292 **[Test build #74659 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74659/testReport)** for PR 17292 at commit

[GitHub] spark issue #17274: [SPARK-19925][SPARKR] Fix SparkR spark.getSparkFiles fai...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17274 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

[GitHub] spark issue #17274: [SPARK-19925][SPARKR] Fix SparkR spark.getSparkFiles fai...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17274 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74661/ Test FAILed. ---

[GitHub] spark issue #17274: [SPARK-19925][SPARKR] Fix SparkR spark.getSparkFiles fai...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17274 **[Test build #74661 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74661/testReport)** for PR 17274 at commit

[GitHub] spark issue #17267: [SPARK-19926][PYSPARK] Make pyspark exception more reada...

Github user uncleGen commented on the issue: https://github.com/apache/spark/pull/17267 @srowen Could you please take a view and help to merge? --- 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] spark issue #17268: [SPARK-19932][SS] Also save event time into StateStore f...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17268 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

[GitHub] spark issue #17268: [SPARK-19932][SS] Also save event time into StateStore f...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17268 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74660/ Test PASSed. ---

[GitHub] spark issue #17268: [SPARK-19932][SS] Also save event time into StateStore f...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17268 **[Test build #74660 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74660/testReport)** for PR 17268 at commit

[GitHub] spark issue #17308: [SPARK-19968][SS] Use a cached instance of `KafkaProduce...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17308 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74658/ Test PASSed. ---

[GitHub] spark issue #17308: [SPARK-19968][SS] Use a cached instance of `KafkaProduce...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17308 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

[GitHub] spark issue #17308: [SPARK-19968][SS] Use a cached instance of `KafkaProduce...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17308 **[Test build #74658 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74658/testReport)** for PR 17308 at commit

[GitHub] spark issue #17314: Openet labs jira spark 15790

Github user ehsun7b commented on the issue: https://github.com/apache/spark/pull/17314 Should I re-open the 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 enabled and

[GitHub] spark issue #17311: [SPARK-19970][SQL] Table owner should be USER instead of...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17311 **[Test build #74664 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74664/testReport)** for PR 17311 at commit

[GitHub] spark issue #17314: Openet labs jira spark 15790

Github user ehsun7b commented on the issue: https://github.com/apache/spark/pull/17314 Yes it is for upstream Spark. Our team is going to contribute on fixing Apache Spark bugs or open JIRA tickets for documentations. --- If your project is set up for it, you can reply to this email

[GitHub] spark issue #17286: [SPARK-19915][SQL] Exclude cartesian product candidates ...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17286 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74656/ Test PASSed. ---

[GitHub] spark issue #17286: [SPARK-19915][SQL] Exclude cartesian product candidates ...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17286 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

[GitHub] spark issue #17286: [SPARK-19915][SQL] Exclude cartesian product candidates ...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17286 **[Test build #74656 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74656/testReport)** for PR 17286 at commit

[GitHub] spark issue #17314: Openet labs jira spark 15790

Github user srowen commented on the issue: https://github.com/apache/spark/pull/17314 OK. Is this intended as a pull request for upstream Spark? (We get a couple accidental PRs a week where someone intended to open a PR against their fork) Reformat the title and explain a bit more

[GitHub] spark issue #17314: Openet labs jira spark 15790

Github user ehsun7b commented on the issue: https://github.com/apache/spark/pull/17314 It's our fork of Apache Spark. --- 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] spark pull request #11601: [SPARK-13568] [ML] Create feature transformer to ...

Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/11601 --- 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] spark issue #11601: [SPARK-13568] [ML] Create feature transformer to impute ...

Github user MLnick commented on the issue: https://github.com/apache/spark/pull/11601 Merged to master. Thanks @hhbyyh and also everyone for reviews. --- 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] spark issue #17314: Openet labs jira spark 15790

Github user srowen commented on the issue: https://github.com/apache/spark/pull/17314 This looks like it is from some other project. What is Openet labs? See http://spark.apache.org/contributing.html --- If your project is set up for it, you can reply to this email and have your

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user jinxing64 commented on the issue: https://github.com/apache/spark/pull/17312 The executor metrics are updated to `StageUIData` when receive executor hear beat. Yes, the longevity of the executor may not cover the whole stage, but it was once active during the stage.

[GitHub] spark issue #17314: Openet labs jira spark 15790

Github user ehsun7b commented on the issue: https://github.com/apache/spark/pull/17314 Why? @srowen --- 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

[GitHub] spark pull request #17314: Openet labs jira spark 15790

Github user ehsun7b closed the pull request at: https://github.com/apache/spark/pull/17314 --- 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] spark issue #17314: Openet labs jira spark 15790

Github user srowen commented on the issue: https://github.com/apache/spark/pull/17314 @ehsun7b close 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 feature enabled and

[GitHub] spark issue #17313: [SPARK-19974][Block Manager] in-memory LRU for partition...

Github user srowen commented on the issue: https://github.com/apache/spark/pull/17313 I don't understand why you say this test doesn't make sense. The assertion is correct. You say you think the second assertion should always pass, but, isn't that the purpose of the test? --- If

[GitHub] spark issue #17314: Openet labs jira spark 15790

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17314 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 project does not have this

[GitHub] spark pull request #17314: Openet labs jira spark 15790

GitHub user ehsun7b opened a pull request: https://github.com/apache/spark/pull/17314 Openet labs jira spark 15790 ## What changes were proposed in this pull request? @Since annotation has been added to all classes at package org.apache.spark.ml This is a partial fix

[GitHub] spark issue #16476: [SPARK-19084][SQL] Implement expression field

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16476 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

[GitHub] spark issue #16476: [SPARK-19084][SQL] Implement expression field

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16476 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74655/ Test PASSed. ---

[GitHub] spark issue #17313: [SPARK-19974][Block Manager] in-memory LRU for partition...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17313 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 project does not have this

[GitHub] spark issue #16476: [SPARK-19084][SQL] Implement expression field

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16476 **[Test build #74655 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74655/testReport)** for PR 16476 at commit

[GitHub] spark pull request #17311: [SPARK-19970][SQL] Table owner should be USER ins...

Github user dongjoon-hyun commented on a diff in the pull request: https://github.com/apache/spark/pull/17311#discussion_r106385533 --- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala --- @@ -851,7 +851,7 @@ private[hive] object HiveClientImpl

[GitHub] spark pull request #17313: [SPARK-19974][Block Manager] in-memory LRU for pa...

GitHub user jianran opened a pull request: https://github.com/apache/spark/pull/17313 [SPARK-19974][Block Manager] in-memory LRU for partitions of multiple RDDs testcase did a get that is no sense ## What changes were proposed in this pull request? in-memory LRU for

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17312 **[Test build #74663 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74663/testReport)** for PR 17312 at commit

[GitHub] spark issue #17251: [SPARK-19910][SQL] `stack` should not reject NULL values...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17251 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74654/ Test PASSed. ---

[GitHub] spark issue #17251: [SPARK-19910][SQL] `stack` should not reject NULL values...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17251 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

[GitHub] spark issue #17251: [SPARK-19910][SQL] `stack` should not reject NULL values...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17251 **[Test build #74654 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74654/testReport)** for PR 17251 at commit

[GitHub] spark pull request #17312: [SPARK-19973] Display num of executors for the st...

GitHub user jinxing64 reopened a pull request: https://github.com/apache/spark/pull/17312 [SPARK-19973] Display num of executors for the stage. ## What changes were proposed in this pull request? In `StagePage` the total num of executors are not displayed. Since executorId

[GitHub] spark issue #17312: [SPARK-19973] Display num of executors for the stage.

Github user srowen commented on the issue: https://github.com/apache/spark/pull/17312 I don't think this is understandable as the executor count. It would also show the total count of executors include dead ones. --- If your project is set up for it, you can reply to this email and

[GitHub] spark pull request #17312: [SPARK-19973] Display num of executors for the st...

Github user jinxing64 closed the pull request at: https://github.com/apache/spark/pull/17312 --- 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] spark issue #17311: [SPARK-19970][SQL] Table owner should be USER instead of...

Github user dongjoon-hyun commented on the issue: https://github.com/apache/spark/pull/17311 Oh, there exists a version issue. Let me fix that. --- 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] spark issue #17312: Display num of executors for the stage.

Github user jinxing64 commented on the issue: https://github.com/apache/spark/pull/17312 @srowen Thanks a lot for quick reply. When we check the reason why a stage ran today much longer than yesterday, we want to know how many executors are supplied. We don't want to count the

[GitHub] spark issue #17312: Display num of executors for the stage.

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17312 **[Test build #74662 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74662/testReport)** for PR 17312 at commit

[GitHub] spark issue #17312: Display num of executors for the stage.

Github user srowen commented on the issue: https://github.com/apache/spark/pull/17312 No, just putting a number in the UI isn't correct. I am not sure this has that much value. This isn't how we manage changes anyway. Please read http://spark.apache.org/contributing.html --- If

[GitHub] spark issue #17310: [SPARK-18579][SQL] Use ignoreLeadingWhiteSpace and ignor...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17310 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74653/ Test PASSed. ---

[GitHub] spark pull request #17312: Display num of executors for the stage.

GitHub user jinxing64 opened a pull request: https://github.com/apache/spark/pull/17312 Display num of executors for the stage. ## What changes were proposed in this pull request? In `StagePage` the total num of executors are not displayed. Since executorId may not be

[GitHub] spark issue #17310: [SPARK-18579][SQL] Use ignoreLeadingWhiteSpace and ignor...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17310 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

<    1   2   3   4   5   6   >