search

thinkaurelius / titan

Distributed Graph Database
http://titandb.io
Apache License 2.0
5.24k stars 1.01k forks source link

"Use Titan's Management API to create indices" #714

Closed asaf closed 10 years ago

asaf commented 10 years ago

Hey,

This is a feature request, to support standard Blueprints API for managing indices,

We'r in a migration process from Neo to Titan and the main reason why this is possible at all without rewrite is thanks to Blueprints,

Not supporting the generic API layer Titan was built on sounds weird to me (unless there's a very good reason)

Support was gone in 0.5.0,

Thanks.

spmallette commented 10 years ago

going forward in tinkerpop3, tinkerpop APIs will not support indexing at all. the vendor indexing APIs are all too varied in what they require to keep the tinkerpop ones generic while still robust. i have a feeling this was a planned move from @mbroecheler given the upcoming shift to TP3 focus.

that said, if you are migrating to titan and are not taking advantage of the native api interface, you won't have a great experience. dig into the titan indexing features as they offer a vast extension over the very limited createKeyIndex feature of Blueprints. furthermore, you will see big performance improvements if you advance your schema beyond basic indices.

i'm sure @mbroecheler will reopen this or comment otherwise if i'm off base here.

asaf commented 10 years ago

@spmallette Thanks for answering,

I understand the complexity of having support for multi vendor within a generic API, and while I dig more and more into Titan, the data type is too different from Neo and other dbs I've seen so far.

Thanks again.

mbroecheler commented 10 years ago

Stephen is exactly right. Also note that the schema and index creation code is typically a small subset of the application that gets executed once and hence the amount of vendor lock in is rather minimal.

And, as Stephen noted, you would typically want to use database specific features. For Titan, a lot of what makes is scalable less in the schema and indexes. On Aug 15, 2014 7:52 PM, "Asaf Shakarchi" notifications@github.com wrote:

@spmallette https://github.com/spmallette Thanks for answering,

I understand the complexity of having support for multi vendor within a generic API, and while I dig more and more into Titan, the data type is too different from Neo and other dbs I've seen so far.

Thanks again.

— Reply to this email directly or view it on GitHub https://github.com/thinkaurelius/titan/issues/714#issuecomment-52302124.