This is an automated email from the ASF dual-hosted git repository.
dkuppitz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/master by this push:
new 855636d Updated TP 4.x design ideas
855636d is described below
commit 855636d46aeb0c48930b6f8c65e5c3831425d5f9
Author: Daniel Kuppitz <[email protected]>
AuthorDate: Thu Nov 29 12:39:58 2018 -0700
Updated TP 4.x design ideas
---
docs/src/dev/future/index.asciidoc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/docs/src/dev/future/index.asciidoc
b/docs/src/dev/future/index.asciidoc
index c77cd26..b973d19 100644
--- a/docs/src/dev/future/index.asciidoc
+++ b/docs/src/dev/future/index.asciidoc
@@ -35,6 +35,7 @@ If adding comments sections, please "sign" comments with
initials and reference
* *spm* - Stephen Mallette
* *as* - Ashwini Singh
+* *dk* - Daniel Kuppitz
image:tp4-think.png[]
@@ -213,3 +214,11 @@ necessarily a GraphSON format and could be something else
as described in the <<
Consider a testing framework based on the Gherkin tests from 3.x and a
`gremlin-test` parent module for all the test
framework modules that will potentially be needed. In 3.x, we found situation
where having test modules beyond
`gremlin-test` would have been helpful, so a parent module that held all those
would probably be smart.
+
+== Elements and IDs
+
+In link:https://issues.apache.org/jira/browse/TINKERPOP-2051[TINKERPOP-2051]
we tried to make vertex property ids local to their vertex. Several approaches
were leading nowhere, in most cases we just broke the Gryo compatibility test
suite. The basic idea was to remember the parent element (at least its id) and
use it in property equality comparisons. This way, the property `[name->marko]`
would only match another `[name->marko]` property if the parent elements were
the same. In the end [...]
+
+=== Comments [dk]
+
+In my opinion, only vertices should have globally unique ids. Edge ids should
be local to the out-vertex (that requires that we "remember" the out-vertex id,
even if the edge is detached) and properties should have no ids at all, they
can be simply identified by their key (or key and value if we decide to keep
multi-properties).
