They you very probably don't have to care about performance and can just use the built-in FTS, see my blog post.
Michael Am 02.09.2014 um 11:14 schrieb Mukesh Khandelwal <[email protected]>: > The use case is that i am creating nodes for users in my organization, and > then provide facility to search for the users. > > > On Tuesday, September 2, 2014 11:56:51 AM UTC+5:30, Michael Hunger wrote: > If you have an efficient implementation of that, right now it might be. We'll > be adding full FTS functionality to cypher in a later release, > right now you can use the legacy full-text-index as you've seen in my blog > post. > > In terms of performance -> Neo4j uses Lucene under the hood, you can > certainly find comparisons between Lucene's approach and implementations > using Tries. > > Also, what is your actual use-case if wildcard search is so critical for you? > > Michael > > Am 02.09.2014 um 06:09 schrieb Mukesh Khandelwal <[email protected]>: > >> Is it better to use a Patricia (Trie) data structure to store the nodes >> that need to be 'wildcard searched' ? >> >> How does the Neo4j match compare with storing the data in a Trie data >> structure in terms of performance, memory, etc? >> >> >> >> On Monday, September 1, 2014 1:19:00 PM UTC+5:30, Michael Hunger wrote: >> You can still use FullTextSearch with legacy indexes and neo4j 2.0, see >> here: http://jexp.de/blog/2014/03/full-text-indexing-fts-in-neo4j-2-0/ >> >> Am 12.08.2014 um 22:42 schrieb Wes Freeman <[email protected]>: >> >>> No. Schema/label indexes are only exact lookups yet. >>> >>> Wes >>> >>> On Tue, Aug 12, 2014 at 4:34 PM, Alan Robertson <[email protected]> wrote: >>> Would it speed up (via indexes) if you added 'n.name >= "Michael"' ? >>> >>> >>> >>> On 08/12/2014 01:13 PM, Wes Freeman wrote: >>>> The way you need to do this (currently) is with the regex syntax: >>>> >>>> MATCH (n) where n.name =~ "Michael.*" RETURN n >>>> >>>> http://docs.neo4j.org/chunked/milestone/query-where.html#_regular_expressions >>>> >>>> Wes >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Neo4j" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Neo4j" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Neo4j" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Neo4j" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
