blueprints createKeyIndex and titan

[Venkatesh Seetharam]

Hi there,

Trust you are doing well. I'm using blueprints API and creating an index for a few property keys. 

graphDB.createKeyIndex(RelationshipGraphBuilder.NAME_PROPERTY_KEY, Vertex.class);

This API does not seem to create an index in Titan since I see quite a few warnings in the logs suggesting to create an index.

Query requires iterating over all vertices [(v[36028797018964674]=ingest-process AND v[36028797018964682]=process-entity)]. For better performance, use indexes (StandardTitanTx:718)

Any idea what am I missing.

Thanks,

Venkatesh

[Daniel Kuppitz]

Hi, Venkatesh,

you probably missed the wiki page Type Definition Overview.

Cheers,

Daniel

--
You received this message because you are subscribed to the Google Groups "Aurelius" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aureliusgraph...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Venkatesh Seetharam]

Thanks Daniel for a quick response and appreciate it. I'm working on an open source project and want to stick to blueprints API with a default Titan implementation. I have looked at this and am aware of this API. But my question was if the blueprints API will indeed translate to the makeKey in Titan or I need to use Titan specific APIs for indexing.

Thanks again,

Venkatesh

[Daniel Kuppitz]

Titans makeKey provides more features than Blueprints createKeyIndex, hence you can't fully translate createKeyIndex into makeKey. Please also see Stephens answer here: Edge keyindex.

Cheers,

Daniel

[Venkatesh Seetharam]

Thanks Daniel for your response. I'm sorry that I'm a newbie but should I have to use Titan API to create an index?

>  The Titan implementation of that creates a very basic index as compared to the full Titan API:

Is this true? I do not see this behavior in Titan.

Thanks,

Venkatesh

[Daniel Kuppitz]

Yes, you should definitely use the Titan API.

>  The Titan implementation of that creates a very basic index as compared to the full Titan API:
Is this true? I do not see this behavior in Titan

No? I think that's exactly what you're seeing, since Titans query optimizer is not able to use a good/full index (and consequently gives you the warning "Query requires iterating over all vertices...").

Cheers,

Daniel

[Venkatesh Seetharam]

Thanks Daniel, you rock!