Cole-Greer commented on code in PR #3523:
URL: https://github.com/apache/tinkerpop/pull/3523#discussion_r3606154733
##########
docs/src/upgrade/release-4.x.x.asciidoc:
##########
@@ -124,43 +122,17 @@ gremlin>
g.V().has('name','marko').dropLabel('employee').labels()
==>manager
```
-The `labels()` step is a flatMap that emits one traverser per label, unlike
`label()` which returns a single string.
-For single-label vertices the two behave identically.
-
-The `mergeV()` step accepts a list for `T.label` to match or create
multi-label vertices. The `onMatch` option uses
-append-only semantics: new labels are added, existing labels are preserved:
-
-```text
-gremlin> g.mergeV([(T.label): ['person','employee'], name: 'marko'])
-==>v[0]
-gremlin> g.mergeV([(T.label): 'person', name: 'marko']).option(Merge.onMatch,
[(T.label): 'director'])
-==>v[0]
-```
-
-By default, `elementMap()` and `valueMap()` continue to return labels as a
single string. To receive all labels as a
-set, use `with("multilabel")` either per-traversal or as a persistent source
configuration:
-
-```text
-// assuming a vertex with labels [person, employee, manager] and name "marko"
-gremlin> g.with("multilabel").V().has('name','marko').elementMap()
-==>{id=0, label=[manager, person, employee], name=marko}
-gremlin> g.V().has('name','marko').elementMap()
-==>{id=0, label=manager, name=marko}
-```
-
-To avoid repeating `with("multilabel")` on every traversal, create a
persistent source:
-
-```text
-gremlin> gml = g.with("multilabel")
-==>graphtraversalsource[tinkergraph[vertices:1 edges:0], standard]
-gremlin> gml.V().has('name','marko').elementMap()
-==>{id=0, label=[manager, person, employee], name=marko}
-gremlin> gml.V().has('name','marko').valueMap(true)
-==>{id=0, label=[manager, person, employee], name=[marko]}
-```
+`mergeV()` accepts a list for `T.label` to match or create multi-label
vertices, with append-only `onMatch`
+semantics. By default `elementMap()` and `valueMap()` still return a single
label string; use `with("multilabel")`,
+per-traversal or as a persistent source, to receive the full set. The
reference documentation covers each of these
+behaviors in detail.
Review Comment:
```suggestion
`mergeV()` now optionally accepts a list for `T.label` to match or create
multi-label vertices. By default
`elementMap()` and `valueMap()` still return a single label string and a new
traversal-source level
`with("multilabel")` config alters the results to wrap labels in lists. The
reference documentation covers each of these
behaviors in detail.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
