Martin Häusler created TINKERPOP-1077:
-----------------------------------------
Summary: @Graph.OptOut should be recognized on graph provider
class as well
Key: TINKERPOP-1077
URL: https://issues.apache.org/jira/browse/TINKERPOP-1077
Project: TinkerPop
Issue Type: Wish
Reporter: Martin Häusler
Priority: Minor
The graph implementation I'm currently working on features a "has-a" reference
to a backend (similar to Titan). The features which are supported by the graph
therefore depend on the chosen backend implementation. However, all backends
are unified by a single Graph class implementation.
Currently, the {{@Graph.OptOut}} annotations have to be put on the graph
class/interface in order to be recognized by the test suite. However, it would
be desirable to have them recognized on the {{GraphProvider}} class as well,
because the graph provider usually has more information about the concrete
graph it instantiates.
A concrete example: one of the backends I am implementing is an in-memory
backend (and yes, I am aware of tinkergraph). One of the graph tests demands
that a graph should be persisted on close. The in-memory backend cannot fulfill
this condition, others might. For each backend, I have a graph provider, so I
could easily attach the {{@Graph.OptOut}} annotation to the in-memory provider.
Attaching it to the whole graph (affecting all backends) makes little sense
here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
