Data Analytics

Announcing retirement of IBM Graph, availability of Compose for JanusGraph

Share this post:


Compose for JanusGraph graph database

We are announcing the retirement of the IBM Graph service on November 27th, 2017. This service is being replaced by Compose for JanusGraph, see below for detailed steps on how to migrate to our new service. The graph database technology at the core of IBM Graph, Titan, has evolved to JanusGraph, which is governed by the Linux Foundation. We are excited to bring this technology, as a production-ready, managed service, to the IBM Cloud.

 

Here’s what you need to know:

End of Marketing Date: November 27th, 2017

As of November 27th, 2017, new IBM Graph instances cannot be provisioned. However, existing instances will continue to be supported.

End of Support Date: April 24th, 2018

  • For a period of 148 days after the End of Marketing Date throughApril 24th, 2018, all existing instances will continue to be available on the Services dashboard in the Bluemix console. All existing instances will also continue to be supported by IBM Graph
  • Any instance still provisioned as of the End of Support Date will be deleted. Please extract data that is still desired as soon as possible
  • Please remember to delete your IBM Graph service instances before the End of Support Date.

Migration: All IBM Graph users can transition to Compose for JanusGraph available in the IBM Bluemix catalog

Any program that makes calls to IBM Graph must adopt the following changes:

  1. The JanusGraph service uses a different endpoint than the IBM Graph service. Users will need to update the service endpoint they’re sending requests to, including the authentication.
  2. The JanusGraph service no longer provides the following endpoints: /schema, /gremlin, /bulkload, /graphs, /index, /vertices, or /edges.
    If you’re using any of these commands, you must change them to send the corresponding gremlin for completing these actions.

    • /schema (modelling): See http://docs.janusgraph.org/latest/schema.htmlfor the Gremlin equivalent modelling
    • /schema (indexing) and /index: See http://docs.janusgraph.org/latest/indexes.htmlfor the Gremlin equivelent indexing
    • /graphs: Graphs are managed in an internal graph which should only be queried. Writing values to this graph will impact the availability of your graphs.
      • list all graphs: janusConfigurationGraph.traversal().V().values(“graph.graphname”);
      • truncate a graph: def graph = ConfiguredGraphFactory.open(graph_name); graph.close(); JanusGraphCleanup.clear(graph); (where graph_name is the name of your graph).
    • /gremlin, /vertices, or /edges: Send gremlin commands as shown in this documentation https://help.compose.com/v2.1/docs/janusgraph-creating-and-accessing-graphs
    • /bulkload: Not currently supported – Users can send gremlin queries for adding the data into JanusGraph using the addVertex() and addEdge() gremlin tasks for each element that needs to be added.
  3. The JanusGraph service no longer provides a graph-specific URL for sending gremlin queries (e.g, https://service_endpoint/service_instance_id/graph_name/gremlin). Users must update their gremlin queries to explicitly open the graph using ConfiguredGraphFactory.open(“graph_name”) and send their gremlin query to the JanusGraph base URI.  Reference: https://help.compose.com/v2.1/docs/janusgraph-creating-and-accessing-graphs
  4. The JanusGraph service does not currently support mixed indices.  You will need to convert them into composite or vertex centric indexes.  This would be a change to your indexes and schema when you initialize your graph: http://docs.janusgraph.org/latest/indexes.html.

For users who have their complete data set locally and tools to upload that data set:

  1. Adapt your tool as described in the previous section.
  2. Stand up a new instance of Compose JanusGraph and run your tool to import the data.
  • You may need to vertically and horizontally scale your JanusGraph Engines temporarily to import your data.  This is currently not available in the Service Management Console.  Contact Bluemix Support to perform this action.
  • You may need to vertically scale your JanusGraph Storage (backend nodes) for optimal performance.  You may do this on service management console by selecting “Scale Resources”.

 

If you don’t have complete copy of your dataset locally, please submit ticket with Bluemix support to get a copy of your data.

 

*This version represents a revised timeline of the IBM Graph Deprecation. 

As always, we’re here to help! Reach out to us in the support forums or on Twitter.

 

 

Offering Manager // Watson Data Platform

Add Comment
No Comments

Leave a Reply

Your email address will not be published.Required fields are marked *

More Products stories

Digital Analytics powered by Watson and the IBM Cloud

Anyone who has walked alongside the pristine fairways and blooming azaleas at Augusta National in early April will tell you the Masters Tournament is unlike any other event in professional sports. The mission of the Masters Digital team is to share this unique experience with the millions of golf fans who are not able to attend. Enabled by IBM as the official IT partner, the team brings new features each year to its digital platforms in hopes of delighting golf fans around the world.

Continue reading

Get Started with Streaming Analytics + Message Hub

Message Hub provides a simple communication mechanism built on Apache Kafka, enabling communication between loosely coupled Bluemix services. This article shows how to communicate with Message Hub from the Streaming Analytics Bluemix service using the messaging toolkit.

Continue reading

Think fast with IBM Streaming Analytics

Learn how IBM clients are moving from batch analytics to real-time streams at Think 2018

Continue reading