[ https://issues.apache.org/jira/browse/SPARK-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010846#comment-14010846 ]
npanj edited comment on SPARK-1153 at 5/28/14 6:48 AM: ------------------------------------------------------- An alternative approach, that I have been using: 1 Use a preprocessing step that maps UUID to an Long. 2. Build graph based on Longs For Mapping in step 1: - Rank your uuids. - some kind of has function? For 1, graphx can provide a tool to generate map. I will like to hear how others are building graphs out of non-Long node types. was (Author: npanj): An alternative approach, that I have been using: 1 Use a preprocessing step that maps UUID to an Long. 2. Build graph based on Longs For Mapping in step 1: - Rank your uuids. - some kind of has function? For 1, graphx can provide a tool to generate map. I will like to hear how others are building graphs out of non-Long node types > Generalize VertexId in GraphX so that UUIDs can be used as vertex IDs. > ---------------------------------------------------------------------- > > Key: SPARK-1153 > URL: https://issues.apache.org/jira/browse/SPARK-1153 > Project: Spark > Issue Type: Improvement > Components: GraphX > Affects Versions: 0.9.0 > Reporter: Deepak Nulu > > Currently, {{VertexId}} is a type-synonym for {{Long}}. I would like to be > able to use {{UUID}} as the vertex ID type because the data I want to process > with GraphX uses that type for its primay-keys. Others might have a different > type for their primary-keys. Generalizing {{VertexId}} (with a type class) > will help in such cases. -- This message was sent by Atlassian JIRA (v6.2#6252)