Skip to content

[SPARK-9912] [MLLIB] QRDecomposition should use QType and RType for type names instead of UType and VType #8140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
mengxr wants to merge 1 commit into from
Closed

[SPARK-9912] [MLLIB] QRDecomposition should use QType and RType for type names instead of UType and VType #8140

mengxr wants to merge 1 commit into from

Conversation

@mengxr
Copy link
Contributor

@mengxr mengxr commented Aug 12, 2015

@SparkQA
Copy link

SparkQA commented Aug 12, 2015

Test build #40672 has finished for PR 8140 at commit 454b27e.

  • This patch fails PySpark unit tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • case class QRDecomposition[QType, RType](Q: QType, R: RType)

@mengxr
Copy link
Contributor Author

mengxr commented Aug 13, 2015

The failed test is unrelated. This is a trivial change. So merged into master and branch-1.5.

@asfgit asfgit closed this in e6aef55 Aug 13, 2015
asfgit pushed a commit that referenced this pull request Aug 13, 2015
@mengxr
[SPARK-9912] [MLLIB] QRDecomposition should use QType and RType for t…
31b7fdc 
…ype names instead of UType and VType

hhbyyh

Author: Xiangrui Meng <meng@databricks.com>

Closes #8140 from mengxr/SPARK-9912.

(cherry picked from commit e6aef55)
Signed-off-by: Xiangrui Meng <meng@databricks.com>
CodingCat pushed a commit to CodingCat/spark that referenced this pull request Aug 17, 2015
@mengxr @CodingCat
[SPARK-9912] [MLLIB] QRDecomposition should use QType and RType for t…
5a89564 
…ype names instead of UType and VType

hhbyyh

Author: Xiangrui Meng <meng@databricks.com>

Closes apache#8140 from mengxr/SPARK-9912.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mengxr @SparkQA