Hi Romiko,
Out of the box auto-indexing only supports exact matches, rather than full text
searches. The reason is that auto indexes are created with the default
configuration (http://docs.neo4j.org/chunked/snapshot/indexing-create.html) the
first time you access them. But this gives us a
Hi Jim
Thanks for the response. I have built a .Net API to manage manual indexes. So
basically when I create a node I have an option to parse in a collection of
key/Val pairs to index the node. I'm using Lucene and fulltext.
However it sounds like auto indexing might be a better option? I
Jim,
To try answer my own question for auto bs manual.
One think I like with manual is a situation where a client had multiple
alsoknownas names which is a relationship IS_ALSO_KNOWN_AS
Now in this case with manual index I can actualy index a reference to client
node using fields from nodes
G'day Romiko,
* Configuration File: Autoindexing enabled here is related to
automatically indexing all nodes and relationships?
*
If I want to add a node to an index following the guidelines, what convention
should be used for the Key/Value naming? Imagine we have nodes of type
Hi,
I am planning to extend the .Net client that we use for CRUD operation and now
add indexing support. I am keen to go the route of AutoIndexing, so we just
query the index and it automatically gets create. Just a few questions.
* Configuration File: Autoindexing enabled here is
5 matches
Mail list logo
