You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Paul Merlin (JIRA)" <ji...@apache.org> on 2017/07/03 18:08:00 UTC
[jira] [Created] (POLYGENE-267) Model extensions capabilities in
tooling
Paul Merlin created POLYGENE-267:
------------------------------------
Summary: Model extensions capabilities in tooling
Key: POLYGENE-267
URL: https://issues.apache.org/jira/browse/POLYGENE-267
Project: Polygene
Issue Type: Wish
Reporter: Paul Merlin
Extensions may have capabilities. Especially implementations of EntityStore and Index/Query.
Here's a non exhaustive list for EntityStore:
- Backup/Restore
- Stream<EntityState> entityStates(), aka. give me everything!
- Optimistic Locking
- etc ...
and for Query:
- query by regex
- query by complex value
- native queries
- etc...
Many of the implementations found in the SDK does not support some of these capabilities. And this can only be deduces from the code at the moment. Ignored tests from {{testsupport}} base test suites are a decent indicator of the situation. But it's totally unconvenient for both users and developers.
We should think about a way to advertise features supported by ES and Index/Query extensions in a way that allow us to report easily and include the information in the generated documentation.
The base test suites could also match the capabilities to make things crystal clear.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)