imbajin commented on code in PR #3349:
URL: https://github.com/apache/hugegraph/pull/3349#discussion_r4283033049


##########
helm/hugegraph/templates/tests/test-connection.yaml:
##########
@@ -16,6 +16,18 @@
 #
 
 {{ include "hugegraph.resolveValues" . }}
+{{- $smoke := `def ids = [] as Set;
+(graph.schema().getVertexLabels() + graph.schema().getEdgeLabels()).each {
+    ids.addAll(it.indexLabels())
+};
+ids.each {
+    def index = graph.indexLabel(it);

Review Comment:
   Confirmed. I used the documentation alternative you proposed: the chart 
README/operations guide and paired English/Chinese website guide now require 
index creation/rebuild jobs to finish before `helm test`, with no concurrent 
schema changes. They explicitly warn that reading an unfinished index on HStore 
can populate other Pods with a stale temporary status, that retries do not 
refresh it, and that affected Server Pods may need replacement after jobs 
finish. The incorrect promise that the retry window lets index work settle is 
removed.
   
   I did not add a task preflight: index creation persists CREATING before the 
rebuild task is saved, so a task scan cannot close that window or prevent new 
work starting after the scan. Task queries can also trigger name-based schema 
loading on a cache miss and mask the stale state under test. The underlying 
cross-Server cache synchronization remains a separate tracked engine issue; 
this documentation correction does not claim to fix it.
   
   Validation: documentation link/path checks and `git diff --check` passed. No 
live service or cluster was started.



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