[
https://issues.apache.org/jira/browse/PIO-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827180#comment-15827180
]
ASF GitHub Bot commented on PIO-47:
-----------------------------------
Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio/pull/328
Cool, that's awesome. This news means the scope has changed, which is great
but brings up the visibility of the id.
Could I suggest that the user-visible engine-instance-id be settable by the
user as a string. The path to template code is already in the metadata--great.
Hash the path by default and report it or allow it optionally to be set with a
string.
As you know I'm proposing that our goal be to have one PIO service that
uses dataset and engine ids to send input and make queries like a DB with
several human named tables. Allowing the user to set the ids makes it possible
to have human readable ones used directly in this future REST API. Like
- `GET /engines/amazon/_query {json query body}` for a query to the
"Amazon" engine
- `GET /engines/netflix/_query {json query body}` for a query to the
"Netflix" engine
Substitute any id you want and use with any template you want. BTW this
method is used in several different REST APIs from MongoDB to Elasticsearch
where tables are named by humans and the ids used in REST.
> 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)
