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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
