A fellow emailed me privately asking me if Blueprints supported Lucene querying over Neo4j.
I said: "No. Neo4jIndex uses index.get(), not index.query()." Then I said: "I shall rectify this."
So I did. Its a bit of a hack, but I think its nice.
Check it:
http://paste.pocoo.org/show/334747/
(NOTE: I'm using full Java notation so its apparent what to do if you are in Blueprints -- not Gremlin).
In short, if you append Neo4jTokens.QUERY_HEADER to your value in a Neo4jIndex.get() call, it will know that you want to do a Lucene-style query. Right now, Neo4jTokens.QUERY_HEADER == "%query%" (WARNING: may change, use Neo4jTokens.QUERY_HEADER to be safe).
Its a hack.... any other ideas are more than welcome. ???
I've committed the code to GitHub and updated Blueprints 0.5-SNAPSHOT in the TinkerPop Maven2 repository with the latest deployment.
LUCA: Does OrientDB support such text searching? Should we add this too OrientGraph?
Thoughts?,
Marko.
> Any way yet to do this from rexster?
Do you mean Lucene wildcards?
Do: key=name&value=%25query%25ma*
-> marko
-> mattias
-> mat
etc.
Marko.
2011/4/16 Marko Rodriguez <okram...@gmail.com>