Re: EdgeId and RelationId using VertexWritable

"" <anjani...@...>

Yes Rafi, even i am doing same for now. 


On Friday, 16 October 2020 at 12:33:27 UTC+5:30 ra...@... wrote:
Hi Anjani

Even I noticed the same (typeId is derived from edgeLabel) but the exact logic is still unknown to me too. For now I am relying on the observation that the typeId remains same for same edgeLabel type and use that for hard-coding the typeId part.




On Wednesday, October 14, 2020 at 4:48:00 PM UTC+5:30 anj...@... wrote:
Hi Rafi,

I am also having same need and was exploring on it. Found that typeId is derived from edgeLabel. EdgeLabel is converted to number using some encloding logic. Though i am not able to figure  exact logic for same but noticed that typeId is always same for same EdgeLabel. Say we have multiple edge with same Label then for all of those edges typeId will be same, rest other 3 param will differ.

Let me know if you were able to figure out more on it.


On Tuesday, 1 September 2020 at 17:00:22 UTC+5:30 ra...@... wrote:
Hi Marc,

I tried to cast the tinkerpop edge to JanusGraph edge but no luck. Is there any way by which I can derive the typeId part of the edgeId myself?

On Wednesday, August 26, 2020 at 2:32:50 PM UTC+5:30 HadoopMarc wrote:
Hi Rafi,

Ok, let's go one step deeper. The StringFactory comes from TinkerPop and does not know about JanusGraph Relationidentifier. The same holds for HadoopGraph. So the HadoopGraph object uses the Edge interface as generic object type for edges. For to return the format you expect from a JanuGraphEdge, the RelationIdentifier.toString() method needs to be called. You can only achieve this by explicitly casting the object to a RelationIdentifier (or maybe by casting edge to a JanusGraphEdge).

HTH,    Marc

Op woensdag 26 augustus 2020 om 09:05:32 UTC+2 schreef ra...@...:
Thanks Marc

I understood the encoding part of the edge_id components. I have few more doubts.
If we look at the example [1zf-388-b2t-368][4184-lives->4112] 
1zf = LongEncoding.encode(2571L) ... RelationId
388 = LongEncoding.encode(4184L) ... Outgoing vertex ID
368 =  LongEncoding.encode(4112L) Incoming vertex ID
b2t = ? ( unknown) ...  From the Relation Identifier , i saw the fourth part is the typeID but what is this and how is it being derived is still unclear to me.

Since I dont have the type ID with me , it seems that the typecasting to RelationIdentifier would not be possible.



On Wednesday, August 26, 2020 at 12:35:54 AM UTC+5:30 HadoopMarc wrote:
Ok, the form [1zf-388-b2t-368][4184-lives->4112] derives from:

return E + L_BRACKET + + R_BRACKET + L_BRACKET + edge.outVertex().id() + DASH + edge.label() + ARROW + edge.inVertex().id() + R_BRACKET;

You can also check in the console:

gremlin> import org.janusgraph.util.encoding.LongEncoding
gremlin> LongEncoding.encode(2571L)
gremlin> LongEncoding.encode(4184L)
gremlin> LongEncoding.encode(4112L)

I guess you have to typecast the result to the JanusGraph RelationIdentifier somehow to get the canonical form you want. My scala is a bit rusty, so I leave that to you.

Btw, it can hardly be a coincidence that someone else had the same problem in a current thread!


Op dinsdag 25 augustus 2020 om 12:50:44 UTC+2 schreef ra...@...:
Hi Everyone,

I am using the VertexWritable class of Janusgraph to fetch the data via Spark as below:
val rdd0: RDD[(NullWritable, VertexWritable)] = spark.sparkContext.newAPIHadoopRDD(hadoopConfiguration, classOf[CqlInputFormat], classOf[NullWritable], classOf[VertexWritable])

val rdd1: RDD[VertexWritable] = { case (x, y) => y.asInstanceOf[VertexWritable] }

When I use => x.edges(Direction.IN)), I get the tinkerpop Edge and the returns the relation ID (e[2571][4184-lives->4112]). How do I get the edge Id ==>e[1zf-388-b2t-368][4184-lives->4112]?

Join to automatically receive all group messages.