You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GetPartitionId algorithm in Exchange is not aligned with Nebula Graph, as a results, string vids with size of 8 might be assigned to a wrong patition, after ingestion, the vertices can't be fetched.
Take a look at the code in Nebula Graph, you will see the main difference is Exchange always hash string vids, while Nebula will take any byte[8] as uint64.
The text was updated successfully, but these errors were encountered:
xiajingchun
added a commit
to xiajingchun/nebula-exchange
that referenced
this issue
Jun 9, 2022
Description
The GetPartitionId algorithm in Exchange is not aligned with Nebula Graph, as a results, string vids with size of 8 might be assigned to a wrong patition, after ingestion, the vertices can't be fetched.
Take a look at the code in Nebula Graph, you will see the main difference is Exchange always hash string vids, while Nebula will take any byte[8] as uint64.
The text was updated successfully, but these errors were encountered: