Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As a first note, <code>embeddedcassandra</code> is no longer what you want in Titan 0.4.0. You can read more about that <a href="https://groups.google.com/forum/#!searchin/aureliusgraphs/embeddedcassandra/aureliusgraphs/EasJTTkDtfY/sPcrWLT9JKsJ">here</a>. In the Titan Server distribution for 0.4.0 cassandra and rexster run in separate JVMs and should generally run out-of-the-box from the distribution. </p> <p>Also note, that I would say it is recommended to create types/indices by way of the Gremlin Console directly. I like being "close to the graph" when working with <code>TypeMaker</code>. You can read more about such production implementation patterns <a href="http://thinkaurelius.com/2013/07/25/developing-a-domain-specific-language-in-gremlin/">here</a>.</p> <p>As for your specific problem, your issue helped uncover a hole in the documentation (which has since been <a href="https://github.com/thinkaurelius/titan/wiki/Rexster-Graph-Server#getting-started-quickly-with-titan-serverzip">remedied</a>). To ensure that elasticsearch gets started with Titan Server make sure that you do:</p> <pre><code>bin/titan.sh -c cassandra-es start </code></pre> <p>At this point you can connect via Rexster to construct and query elasticsearch indices. Here's an example from Rexster Console:</p> <pre><code>rexster[groovy]&gt; g = rexster.getGraph("graph") ==&gt;titangraph[cassandra:null] rexster[groovy]&gt; g.makeKey("name").dataType(String.class).indexed("search",Vertex.class).make() ==&gt;v[74] rexster[groovy]&gt; g.commit() ==&gt;null rexster[groovy]&gt; g.addVertex([name:'marko']) ==&gt;v[4] rexster[groovy]&gt; g.addVertex([name:'stephen']) ==&gt;v[8] rexster[groovy]&gt; g.commit() ==&gt;null rexster[groovy]&gt; g.V.has('name',PREFIX,'mar') ==&gt;v[4] </code></pre> <p>Note that by starting Titan Server in this mode, elasticsearch is running in <a href="https://github.com/thinkaurelius/titan/wiki/Using-Elastic-Search#elasticsearch-embedded-configuration">embedded mode</a> to the Titan instance started by Rexster which means that:</p> <blockquote> <p>Elasticsearch will not be accessible from outside of this particular Titan instance, i.e., remote connections will not be possible</p> </blockquote> <p>So if you are trying to connect via a Titan Gremlin Console, I don't believe it will work. Connections have to run through Rexster.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to actually set up basic Titan + Rexster + Cassandra?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USstephen mallette
    1. USstephen mallette
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to actually set up basic Titan + Rexster + Cassandra?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAlright, that seems to be starting. What index name should I use? In the documentation it says that you make elasticsearch indices like this: `graph.makeKey("reason").dataType(String.class).indexed("search",Vertex.class).indexed("search", Edge.class).make()`. When I do this I get an error, which I guess is because the `search` index does not exist (the stack trace won't show). How do I fix this?
      singulars
      1. PO
      1. USAutomatico
    2. COWhere are you trying to create the index from? Rexster Console?
      singulars
      1. PO
      1. USstephen mallette
    3. COExpanded my answer a bit to show index creation. Again, no extra configuration was required here...works out of the box.
      singulars
      1. PO
      1. USstephen mallette
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload