[
https://issues.apache.org/jira/browse/MAHOUT-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305980#comment-15305980
]
ASF GitHub Bot commented on MAHOUT-1866:
----------------------------------------
GitHub user smarthi opened a pull request:
https://github.com/apache/mahout/pull/237
MAHOUT-1866: Add matrix-to-tsv string function
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/smarthi/mahout MAHOUT-1866
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/mahout/pull/237.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #237
----
commit 16dbcdd63e457c8a1956394a9fefdc5aae3f2d18
Author: smarthi <[email protected]>
Date: 2016-05-29T16:27:50Z
MAHOUT-1866: Add matrix-to-tsv string function
----
> Add matrix-to-tsv string function
> ---------------------------------
>
> Key: MAHOUT-1866
> URL: https://issues.apache.org/jira/browse/MAHOUT-1866
> Project: Mahout
> Issue Type: Sub-task
> Reporter: Trevor Grant
> Assignee: Suneel Marthi
> Fix For: 0.13.0
>
>
> Need a function to convert a matrix to a tsv string which can then be plotted
> by
> - Zeppelin %table visualization packages
> - Passed to R / Python via Zeppelin Resource Manager
> It has been noted that a matrix can be registered as an RDD and passed across
> contexts directly in Spark, however this breaks the 'backend agnoistic'
> philosophy. Until H20 and Flink also both support Python / R environments it
> is more reasonable to use tab-seperated-value strings.
> Further, matrices might be extremely large and unfit for being directly
> converted to tsvs. It may be wise to introduce some sort of safety valve for
> preventing excessively large matrices from being materialized into local
> memory (eg. supposing the user hasn't called their own sampling method on a
> matrix).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
