[ 
https://issues.apache.org/jira/browse/TINKERPOP-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539460#comment-17539460
 ] 

ASF GitHub Bot commented on TINKERPOP-2745:
-------------------------------------------

spmallette commented on code in PR #1659:
URL: https://github.com/apache/tinkerpop/pull/1659#discussion_r876908792


##########
gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/computer/clustering/connected/ConnectedComponentVertexProgram.java:
##########
@@ -43,12 +44,10 @@
 import org.apache.tinkerpop.gremlin.structure.Vertex;
 import org.apache.tinkerpop.gremlin.structure.VertexProperty;
 
-import java.util.Arrays;
-import java.util.Collection;
-import java.util.Collections;
-import java.util.HashSet;
-import java.util.Iterator;
-import java.util.Set;
+import java.util.*;

Review Comment:
   nit: please check your IDE settings - looks like it added a wildcard import. 
the tinkerpop style is to be explicit with import





> Add getter for vertex properties in vertex programs
> ---------------------------------------------------
>
>                 Key: TINKERPOP-2745
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2745
>             Project: TinkerPop
>          Issue Type: Improvement
>            Reporter: Boxuan Li
>            Priority: Major
>
> Many if not all vertex programs will mutate vertex properties during the 
> computation process. For graphs that enforce a schema, this could lead to 
> failure. JanusGraph, for example, when used with FulgoraGraphComputer and 
> disabled automatic schema maker, will report error for vertex programs. See 
> [https://gitter.im/janusgraph/janusgraph?at=626c568910cfc315bc5781a0]
>  
> This ticket proposes a getter method for each vertex program, which would 
> return the vertex properties together with their data types needed in the 
> computation. The graph providers or users could then leverage this 
> information to create the corresponding schema.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to