Skip to content

Conversation

@viirya
Copy link
Member

@viirya viirya commented May 5, 2015

JIRA: https://issues.apache.org/jira/browse/SPARK-7245

Besides, CovarianceCounter.merge has a bug that sometimes other.count could be zero. It makes the results incorrect (NaN). This pr fixes it and a minor typo in CovarianceCounter too.

@SparkQA
Copy link

SparkQA commented May 5, 2015

Test build #31829 has finished for PR 5902 at commit 32f511d.

  • This patch fails to build.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented May 5, 2015

Test build #31844 has finished for PR 5902 at commit 92b4ab9.

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

@rxin
Copy link
Contributor

rxin commented May 6, 2015

@viirya can you submit a separate PR for the bug fix? The bug fix should go into 1.4, and the rest can go into 1.5.

@viirya
Copy link
Member Author

viirya commented May 6, 2015

ok.

@viirya
Copy link
Member Author

viirya commented May 6, 2015

Submitted the bug fixing of CovarianceCounter.merge to #5931.

@srowen
Copy link
Member

srowen commented Aug 11, 2015

@viirya you still have ~14 open PRs, some of which have been out there for months. This is an example of one that doesn't seem to have traction; can you close these out including the JIRA?

@rxin
Copy link
Contributor

rxin commented Aug 11, 2015

@viirya we should close this one for now, and re-open it later when we do this as an aggregate function.

@viirya
Copy link
Member Author

viirya commented Aug 11, 2015

Sure. No problem.

@viirya viirya closed this Aug 11, 2015
@viirya
Copy link
Member Author

viirya commented Aug 11, 2015

@srowen The JIRA is not open by me, is it ok to close it by me?

@rxin
Copy link
Contributor

rxin commented Aug 11, 2015

I think he meant closing the github pull request for now - not the JIRA ticket. Thanks!

@srowen
Copy link
Member

srowen commented Aug 11, 2015

Yes @viirya thanks for the PR; I really mean we should only keep PRs open while they're 'active' and close them if they're not obviously moving forward. They can come back later if needed. I just noticed this morning you still had a number that had been inactive for over a month.

In this case, I think the JIRA could be closed too, though it's more debatable. You don't need to close the JIRA if in doubt. One Of These Days we'll go through and start auto-closing long-inactive JIRAs too.

@viirya
Copy link
Member Author

viirya commented Aug 11, 2015

@srowen Thanks for explaining that. I already closed some other PRs together.

@viirya viirya deleted the spearman_corr branch December 27, 2023 18:17
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.

4 participants