[
https://issues.apache.org/jira/browse/TINKERPOP3-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717761#comment-14717761
]
Matthias Broecheler commented on TINKERPOP3-691:
------------------------------------------------
Yes, I could reuse the wrapper but that would mean a lot of overhead in the
vertex program execution just so I know in what context the exception occurs.
In general, I do not see the necessity to to dictate the exact type of
exception that is being accepted and in this particular instance it is quite
difficult to deal with it without wrapping the vertex.
> TP3 is too prescriptive in exception
> ------------------------------------
>
> Key: TINKERPOP3-691
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-691
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.0.0-incubating
> Reporter: Matthias Broecheler
> Priority: Minor
>
> In its current state, TP3 is extremely prescriptive about the exact type of
> exception that should be thrown in certain situations. Sometimes these
> exceptions are symptoms of the same behavior (i.e. accessing properties you
> shouldn't) but are different based on the access path (i.e. there are
> separate exceptions for MapReduce and VertexProgram when such access happens).
> This makes it cumbersome for vendors to implement TP3 because you have to
> know in core datastructures where they are being used even though the
> datastructure can be reused between components.
> An example of that is PreloadedVertex in Titan where we have to store in what
> context such a vertex is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
