Current implementation use to vertexId as qualifier. This will be problematic if user request update on popular from vertexId. problem is one region server is responsible for snapshotEdge. I suggest spread snapshotEdge across multiple region by using composite of (from, to) vertexId as rowKey and empty qualifier.
hsleep
commented
8 years ago
Current implementation use to vertexId as qualifier. This will be problematic if user request update on popular from vertexId. problem is one region server is responsible for snapshotEdge. I suggest spread snapshotEdge across multiple region by using composite of (from, to) vertexId as rowKey and empty qualifier.