You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@madlib.apache.org by "Nandish Jayaram (JIRA)" <ji...@apache.org> on 2018/11/27 17:35:00 UTC
[jira] [Commented] (MADLIB-1171) Support model versioning in output
tables
[ https://issues.apache.org/jira/browse/MADLIB-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700768#comment-16700768 ]
Nandish Jayaram commented on MADLIB-1171:
-----------------------------------------
The above two comments from ASF GitHub Bot is probably because this Jira was linked
in some other commit/PR by mistake. They should be ignored.
> Support model versioning in output tables
> -----------------------------------------
>
> Key: MADLIB-1171
> URL: https://issues.apache.org/jira/browse/MADLIB-1171
> Project: Apache MADlib
> Issue Type: New Feature
> Components: All Modules
> Reporter: Frank McQuillan
> Assignee: Nikhil
> Priority: Major
> Fix For: v2.0
>
> Attachments: model-versioning-work1.pdf, model-versioning-work2.pdf, p100.png, p101.png
>
>
> Context
> For many MADlib modules, <out_table> contains the separate models for each group and <out_table>_summary contains the common model data for all groups. Modeling versioning can be awkward since the model output table and model summary table need to be explicitly dropped between runs.
> Story
> As a data scientist, I want to perform multiple runs without having to drop tables, so that I can easily get a history of the model runs with clear versioning.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)