[
https://issues.apache.org/jira/browse/TINKERPOP-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092437#comment-18092437
]
ASF GitHub Bot commented on TINKERPOP-3261:
-------------------------------------------
spmallette commented on code in PR #3483:
URL: https://github.com/apache/tinkerpop/pull/3483#discussion_r3494541132
##########
gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/traversal/dsl/graph/GraphTraversal.java:
##########
@@ -1466,6 +1484,30 @@ public default GraphTraversal<S, Vertex> addV() {
return this.asAdmin().addStep(new
AddVertexStepPlaceholder<>(this.asAdmin(), (String) null));
}
+ /**
+ * Adds a {@link Vertex} with multiple labels. Use this method to create
multi-labeled vertices.
+ * Creates the vertex with the first label, then adds the remaining labels.
+ *
+ * @param label1 the first label
+ * @param label2 the second label
+ * @param moreLabels additional labels
+ * @return the traversal with the {@link AddVertexStepContract} added
+ * @since 4.0.0
+ */
+ public default GraphTraversal<S, Vertex> addV(final String label1, final
String label2, final String... moreLabels) {
Review Comment:
was it intentional to skip the multi-variation of `addV(Traversal)`? Is the
intent to push those folks to `addLabel(Traversal)` or something?
> Enable multiple label support on vertex with configurable label cardinality
> ---------------------------------------------------------------------------
>
> Key: TINKERPOP-3261
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3261
> Project: TinkerPop
> Issue Type: Task
> Affects Versions: 4.0.0
> Reporter: Yang Xia
> Priority: Major
>
> Vertices are currently limited to a single immutable label assigned at
> creation. This prevents modeling common real-world scenarios where entities
> naturally belong to multiple categories (e.g., a person who is both an
> employee and a manager).
>
> Introduce a configurable LabelCardinality that controls how many labels a
> vertex may have and whether they can be mutated after creation. Three
> proposed modes: ONE (current behavior, default), ONE_OR_MORE (mutable,
> minimum one), ZERO_OR_MORE (fully flexible).
>
> New steps:
>
> - labels() — flatMap step emitting each label as a traverser
> - addLabel(String, String...) — add labels to a vertex
> - dropLabel(String, String...) — remove specific labels
> - dropLabels() — remove all labels
> Edge labels remain at cardinality ONE. The infrastructure would support
> future edge multi-label enablement without wire format changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
