What I think is the core of the index REST story is that we need to add the query part of things to it, not just the exact matching (index.get() and index.query()). You can do that easily writing a server plugin, I will try to do it during my next lab day, but the basics go like http://docs.neo4j.org/chunked/snapshot/server-plugins.html
Would that help? /peter On Wed, Feb 9, 2011 at 10:25 PM, Michael Hunger <[email protected]> wrote: > Tom, > > What do you mean with graphdb.index("whatever") > > the (new) indexing API that is available since 1.2 has the syntax > graphDb.index().forNodes("indexName").add(node,key,value) for adding to the > index and > IndexHits<Node> hits = graphDb.index().forNodes("indexName").get(key,value) > > and this is supported by the REST API, see: > http://components.neo4j.org/neo4j-server/milestone/rest.html#Add_to_index > > Hope that helps > > Michael > > > Am 09.02.2011 um 16:31 schrieb Tom Smith: > >> Hello, >> >> I tried using the REST server (which is great) but it doesn't support >> graphdb.index("whatever") yet. >> >> When will the next release of the REST server (with indexing) or the python >> binding? >> >> Thanks >> >> Tom Smith > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
