[ 
https://issues.apache.org/jira/browse/FLINK-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980911#comment-14980911
 ] 

ASF GitHub Bot commented on FLINK-1966:
---------------------------------------

Github user smarthi commented on the pull request:

    https://github.com/apache/flink/pull/1186#issuecomment-152265442
  
    Suggest that you see how PMML been's done on Oryx 2.0 (PMML in Spark 
followed Oryx 2.0).  PMML support was discussed various times on the Mahout 
project and was never implemented in large part due to lack of actual PMML 
usage by Machine Learning Practitioners and Data Scientists. 
    
    See this Mahout thread from last year and more specifically to Ted 
Dunning's comment in the thread - 
http://mail-archives.apache.org/mod_mbox/mahout-dev/201503.mbox/%3CCAJwFCa1%3DAw%2B3G54FgkYdTH%3DoNQBRqfeU-SS19iCFKMWbAfWzOQ%40mail.gmail.com%3E
    
    Given that PMML models could possibly get real huge, its a good practice to 
persist them in compressed format. It would also be good to be able to specify 
which features/fields are categorical/numeric (via a config file maybe). 
    
    
    
    
    
    



> Add support for predictive model markup language (PMML)
> -------------------------------------------------------
>
>                 Key: FLINK-1966
>                 URL: https://issues.apache.org/jira/browse/FLINK-1966
>             Project: Flink
>          Issue Type: Improvement
>          Components: Machine Learning Library
>            Reporter: Till Rohrmann
>            Assignee: Sachin Goel
>            Priority: Minor
>              Labels: ML
>
> The predictive model markup language (PMML) [1] is a widely used language to 
> describe predictive and descriptive models as well as pre- and 
> post-processing steps. That way it allows and easy way to export for and 
> import models from other ML tools.
> Resources:
> [1] 
> http://journal.r-project.org/archive/2009-1/RJournal_2009-1_Guazzelli+et+al.pdf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to