Copilot commented on code in PR #240:
URL: 
https://github.com/apache/incubator-hugegraph-ai/pull/240#discussion_r2097122912


##########
hugegraph-llm/src/hugegraph_llm/utils/graph_index_utils.py:
##########
@@ -47,9 +47,10 @@ def get_graph_index_info():
 
 def clean_all_graph_index():
     VectorIndex.clean(str(os.path.join(resource_path, 
huge_settings.graph_name, "graph_vids")))
+    VectorIndex.clean(str(os.path.join(resource_path, 
huge_settings.graph_name, "graph_props")))
     VectorIndex.clean(str(os.path.join(resource_path, "gremlin_examples")))
-    log.warning("Clear graph index and text2gql index successfully!")
-    gr.Info("Clear graph index and text2gql index successfully!")
+    log.warning("Clear graph index, property index and text2gql index 
successfully!")
+    gr.Info("Clear graph index, property index and text2gql index 
successfully!")

Review Comment:
   The log message references 'text2gql' but the feature is called 
'text2gremlin'. Consider updating it to 'text2gremlin index' and using past 
tense for consistency (e.g., 'Cleared...').
   ```suggestion
       log.warning("Cleared graph index, property index, and text2gremlin index 
successfully!")
       gr.Info("Cleared graph index, property index, and text2gremlin index 
successfully!")
   ```



##########
hugegraph-llm/src/hugegraph_llm/operators/hugegraph_op/fetch_graph_data.py:
##########
@@ -49,4 +50,19 @@ def res = [:];
 
         if isinstance(result, list) and len(result) > 0:
             graph_summary.update({key: result[i].get(key) for i, key in 
enumerate(keys)})
+
+        index_labels = self.schema.getIndexLabels()

Review Comment:
   [nitpick] Add or update the docstring for `run` to explain how 
`index_labels` is populated and used downstream for property embedding, so 
future maintainers understand this new field in `graph_summary`.



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to