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

ASF GitHub Bot commented on PIO-47:
-----------------------------------

Github user pferrel commented on the issue:

    https://github.com/apache/incubator-predictionio/pull/328
  
    Ideally `pio build` and `pio train` should run anywhere by supplying any 
params needed.
    
    @chanlee514 metadata still is needed in a service like Elasticsearch so 
every place the model is deployed will know the params. When is engine.json etc 
written to the metastore?


> Remove engine manifest for stateless build
> ------------------------------------------
>
>                 Key: PIO-47
>                 URL: https://issues.apache.org/jira/browse/PIO-47
>             Project: PredictionIO
>          Issue Type: New Feature
>            Reporter: Chan
>
> As discussed in the dev mailing list, removing engine manifest would be the 
> first step in improving the workflow towards a more modular design. 
> - Remove manifest.json completely. `pio build` will be stateless, and will 
> not write anything to the database. This will make it easier to compile/build 
> on PaaS platforms such as Heroku. Later, we can remove `pio build` command 
> entirely, so that PIO is independent of the build tool (sbt).
> - An immediate major disadvantage would be not being able to run pio commands 
> outside of the engine directory. This can be resolved in the next step of 
> creating a general metadata registry.
> - Meanwhile, we can use engineFactory as *engineId* , and SHA-1 hash of 
> engine filepath as *engineVersion* (as before). We can improve this when 
> designing a metadata registry, 



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

Reply via email to