Skip to content

Conversation

@piganesh
Copy link
Contributor

No description provided.

@srowen
Copy link
Member

srowen commented Jul 14, 2015

This needs a proper title and description.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this fix the issue mentioned in SPARK-8695?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, @mengxr was your intent to add the condition numPartitions > 5?
Also, I don't think you need to change the current condition; it's fine. (BTW .toDouble is a better idiom for casting than 1.0 *)

@sarutak
Copy link
Member

sarutak commented Jul 15, 2015

@piganesh When you open a PR, you should put a proper title and description.
Also, you should add proper tags like [CORE] , [MLlib]. and so on.
In this case, the title should be like [SPARK-8695][CORE][MLlib] TreeAggregation shouldn't be triggered for 5 partitions.

See also https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark

@srowen
Copy link
Member

srowen commented Jul 19, 2015

(Ah: this continues a discussion in #7168 -- should have been mentioned in this PR.)

@piganesh do you mind closing this if you're not going to follow up?
Otherwise, please make the .toDouble change and correctly title this PR.

@piganesh
Copy link
Contributor Author

Sean

I did generate a new patch based on mengxr 's comment

Namely

while (numPartitions > scale + math.ceil(1.0 * numPartitions / scale))

and submitted a pull request ..

thanks

  • P. I.

@srowen
Copy link
Member

srowen commented Jul 19, 2015

@piganesh ... yes, that's this one. I've added a review comment last week, which you should act on.

@piganesh
Copy link
Contributor Author

I had made the changes to use ceiling instead of the hard coded greater
than
5 check and submitted a pull request through ibmsoe github.

I need to check why you are not able to view the change. Give me a day.

thanks

From: Sean Owen [email protected]
To: apache/spark [email protected]
Cc: P I Ganesh/Austin/IBM@IBMUS
Date: 07/19/2015 04:58 PM
Subject: Re: [spark] Spark 8695 (#7397)

@piganesh ... yes, that's this one. I've added a review comment last week,
which you should act on.

Reply to this email directly or view it on GitHub.

@piganesh
Copy link
Contributor Author

OK I understood now. You had a comment on top to use .toDouble. Shall get to it ASAP. Sorry for the confusion.

@piganesh
Copy link
Contributor Author

Submitting a new pull request

@piganesh piganesh changed the title Spark 8695 [SPARK-8695][CORE][MLlib] TreeAggregation shouldn't be triggered when it doesn't save wall-clock time. Jul 21, 2015
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM except the parens around (numPartitions) aren't needed. That's trivial though.

@srowen
Copy link
Member

srowen commented Jul 21, 2015

OK to test

@SparkQA
Copy link

SparkQA commented Jul 21, 2015

Test build #1148 has finished for PR 7397 at commit 041620c.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@sarutak
Copy link
Member

sarutak commented Jul 21, 2015

retest this please.

@mengxr
Copy link
Contributor

mengxr commented Jul 21, 2015

@piganesh You don't need to make a new PR for updates. You can push new commits to your remote branch, which you used to create the PR. Please address @srowen 's comment and remove (...) around numPartitions. Thanks!

@SparkQA
Copy link

SparkQA commented Jul 21, 2015

Test build #37956 has finished for PR 7397 at commit 041620c.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@srowen
Copy link
Member

srowen commented Jul 23, 2015

Since this is taking a while to finish relative to the tiny change, I made this last change myself and merged to master.

@asfgit asfgit closed this in b983d49 Jul 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants