[
https://issues.apache.org/jira/browse/ATLAS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194819#comment-15194819
]
Hemanth Yamijala commented on ATLAS-517:
----------------------------------------
[~cassiodossantos], Maybe the right step forward is to file a JIRA for
addressing the HBase change specifically and we can see how best to support. It
would also greatly help push this if you can think of any specific improvements
the later versions would make to Atlas specifically. Regarding Titan 1.x move,
we have these discussions on going, but like in your case, there are versions
we need to support from a platform perspective as well and that causes some
dependencies, thereby taking time to resolve.
> Upgrade titan to 1.x
> --------------------
>
> Key: ATLAS-517
> URL: https://issues.apache.org/jira/browse/ATLAS-517
> Project: Atlas
> Issue Type: Wish
> Affects Versions: trunk
> Reporter: Nigel Jones
>
> titan 0.54 currently ships with, and is supported by, Atlas.
> This itself officially supports
> - Cassandra 1.2.z, 2.0.z
> - HBase 0.94.z, 0.96.z, 0.98.z
> - ElasticSearch 1.0.z, 1.1.z, 1.2.z
> - Solr 4.8.1
> - Tinkerpop 2.5.z
> souce: http://s3.thinkaurelius.com/docs/titan/0.5.4/version-compat.html
> As of 24 Feb 2015 titan 1.0.0 is current and supports
> - Cassandra 1.2.z, 2.0.z, 2.1.z (ADDS support for 2.1)
> - HBase 0.94.z, 0.96.z, 0.98.z, 1.0.z (ADDS support for 1.0)
> - ElasticSearch 1.0.z, 1.1.z, 1.2.z (DROPS these, ADDS 1.5)
> - Solr 5.2.z (DROPS 4.8.1, ADDS 5.2.z)
> - Tinkerpop 3.0.z (DROPS 2.5, ADDS 3.0)
> In addition in the titan community 1.1 is now being built, and there are
> discussions around tinkerpop 3.1 support, as well as hadoop2
> source:
> https://groups.google.com/forum/#!searchin/aureliusgraphs/1.1/aureliusgraphs/e5L5M6MQozY/QHXtx5hFAwAJ
> I would like to be able to use current versions of titan as my graph store in
> order to be able to benefit from
> - a platform on which to better integrate with tinkerpop (see separate issue
> to be raised)
> - improvements in indexing
> - more recent HBase and Cassandra support for underlying storage
> Given titan 1.1 is imminent I would be inclined to aim for that as a target &
> perhaps we should start experimenting with titan 1.0 since there have been
> API changes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
