[jira] [Commented] (ATLAS-517) Upgrade titan to 1.x

["CASSIO DOS SANTOS (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193853#comment-15193853 ] 

CASSIO DOS SANTOS commented on ATLAS-517:
-----------------------------------------

[~yhemanth] I wanted to check if there has been any activity / discussion on that front on your side, and any updates to your plan. Our cloud platform supports more recent stable versions of some of the products Atlas depends on, like Titan 1.x and HBase 1.2.x, and having to deploy with older versions prevents us from leveraging many of the management services available on the newer versions, not to mention the fact that some of those older versions are no longer supported by their providers. 

I understand that in this particular case you have the additional challenge of moving to Java 8, but in the more general case, it seems that the ability to more quickly validate and support newer versions of the underlying data stores may become more critical in environments like the cloud. I've noticed that the Atlas code has some mechanisms in place to address that on top of what Titan provides. If getting Atlas supported on top of Titan 1.x is going to require more work and take longer, one temporary option that may work for us is to get Titan 0.54 to work on top of HBase 1.2.x, which could require some changes to the Atlas code that would likely be  much more localized and less disruptive that a full port to the latest version of Titan.



> 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)