ASF GitHub Bot commented on PIO-47:

Github user chanlee514 commented on the issue:

    @pferrel: I agree, and that would be possible with a general metadata 
registry server which would be the next step. The reason I started by removing 
manifest.json is because the previous database-dependent build was a roadblock 
for PredictionIO in PaaS platforms such as Heroku. 
    Information in engine.json is written during `pio train` as engineInstance.

> 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

Reply via email to