Closed jturmel closed 8 years ago
I think it should technically be possible to implement KeyValueStore against BigTable.
This is now a duplicate of 1203. Recommend we close either this one or 1203, and not sure this needs an issue open against Titan, unless the idea is Titan include a titan-bigtable module, which doesn't seem like a good idea.
Closing in favor #1203 as @graben1437 suggested.
Seems weird since this one was opened/existed first... but anyhow. :smile:
If it makes you feel any better, I suspect the other will be closed as well before we're all done going through issues. :)
When it comes to new backends for Titan, we generally like to see folks develop those externally in their own repositories, get community feedback and then watch how it evolves. Amazon did this nicely. I think MapDB has an implementation in the works like that.
I know, mostly kidding.
On Thu, Dec 17, 2015, 10:00 AM stephen mallette notifications@github.com wrote:
If it makes you feel any better, I suspect the other will be closed as well before we're all done going through issues. :)
When it comes to new backends for Titan, we generally like to see folks develop those externally in their own repositories, get community feedback and then watch how it evolves. Amazon did this nicely. I think MapDB has an implementation in the works like that.
— Reply to this email directly or view it on GitHub https://github.com/thinkaurelius/titan/issues/1117#issuecomment-165493678 .
@jturmel, @graben1437 — you can use JanusGraph (fork of Titan) together with Bigtable; see JanusGraph + Bigtable docs for configuration details.
They use the HBase API, but have some slight differences.
HBase differences: https://cloud.google.com/bigtable/docs/hbase-differences