I think I figured out the reason why the vertices were not getting loaded. The atlas jars also need to be copied into REXHOME/ext/titan to make it work.
ATLAS as you might be ware is using berkeley DB and ES as the default storage and index backends . You need to configure that in the rextser.xml conf pointed out in the above link and point to the directory where the data for them resides. Connecting through the gremlin shell also requires a .properties file with all these properties set to load the graph stored by ATLAS. Thanks Suma On Fri, Sep 4, 2015 at 5:47 PM, Suma Shivaprasad < sumasai.shivapra...@gmail.com> wrote: > Hi Nigel, > > You should be able to point to the graph created in ATLAS through Rexster > by following the steps at > http://s3.thinkaurelius.com/docs/titan/current/server.html#_downloading_rexster_and_titan_separately. > I was able to get the Rexster instance up this way but got some issue while > loading the vertices though the edges are seen. Need to dig into this > further. > > Thanks > Suma > > > On Thu, Sep 3, 2015 at 8:47 PM, Nigel Jones <jon...@uk.ibm.com> wrote: > >> >> >> I'm trying to understand more about the setup/configuration - for example >> I'd like to improve my understanding of atlas by: >> - Use the titan rexster api to view/understand the underlying graph >> - using titans doghouse UI to poke around >> - use the gremlin shell >> >> In the Atlas Configuration documentation i can see reference to modifying >> the underlying titan storage backend & a few other aspects of config. >> >> Atlas comes with the 0.5.4 titan jars, but not the full distribution >> >> Before I start trying to add in rexster etc I was wondering if anyone >> else has done this & what the appropriate approach might be >> >> Thanks >> Nigel. >> >> >> >> >> >
