Hi, thanks for the quick update. I'd also need some kind of
"comparator" (greaterThan, contains, etc) passed in to that method as
well, in order to form the proper Lucene Query. The other trick is
considering nodes which have been modified/added/deleted in the
current Lucene transaction.
I think
More info about that at http://components.neo4j.org/index-util/
2009/7/1 Mattias Persson :
> Great initiative, btw have you looked at the
> LuceneFulltextIndexService in the same package? It might be able to do
> what you're asking for.
>
> By @Overriding the formQuery method you can construct wha
Great initiative, btw have you looked at the
LuceneFulltextIndexService in the same package? It might be able to do
what you're asking for.
By @Overriding the formQuery method you can construct whatever queries
you like based on key and search value (I just altered the signature
to also take the k
3 matches
Mail list logo
