contrueCT commented on issue #3095:
URL: https://github.com/apache/hugegraph/issues/3095#issuecomment-5200792914

   Thanks for reporting this issue.
   
   This problem appears to be related to the HStore `graphId` isolation bug 
that is currently being fixed in the community repository:
   
   https://github.com/hugegraph/hugegraph/pull/163
   
   In HugeGraph 1.7.0, the HStore batch `put` and `merge` paths used 
`InnerKeyCreator#getKey()`. When a graph did not yet have a persisted 
`graphId`, this method could use the missing-graph sentinel value instead of 
allocating a new ID. As a result, multiple newly created graphs could use the 
same internal key prefix and access the same underlying vertex data.
   
   PR #163 changes these write paths to use `getKeyOrCreate()`, ensuring that 
each graph receives its own `graphId` before data is written. It also adds 
graph ID collision checks and a regression test that writes the same key to two 
different graphs and verifies that their data remains isolated.
   
   Therefore, PR #163 should address the root cause of the cross-GraphSpace and 
cross-graph data leakage described in this issue. The PR is still under review, 
and the fix will be merged into the ASF master branch and included in a future 
official release.
   


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