Dennis,
I've attached some sample code that works well for my needs. You should
find it scales very well, even when you search for a "parentpath" near
the root.
The output I get from running this program is:
query: name:rt.jar
D:\opt\j2sdk1.4.2\jre\lib\rt.jar
query: name:LICENSE
D:\opt\j2sd
Dennis Thrysøe wrote:
Andrzej Bialecki wrote:
Anyway.. I should've added that for Phrase Queries to work the text
must be tokenized. So, the best way in this case would be to use
WhitespaceAnalyzer for the uri field,
I've figured out how to use the WhitespaceAnalyzer for creating the
PhraseQ
PerFieldAnalyzerWrapper ?
Otis
--- Dennis_Thrysøe <[EMAIL PROTECTED]> wrote:
> Andrzej Bialecki wrote:
> > Anyway.. I should've added that for Phrase Queries to work the text
> must
> > be tokenized. So, the best way in this case would be to use
> > WhitespaceAnalyzer for the uri field,
>
> I'
Andrzej Bialecki wrote:
Anyway.. I should've added that for Phrase Queries to work the text must
be tokenized. So, the best way in this case would be to use
WhitespaceAnalyzer for the uri field,
I've figured out how to use the WhitespaceAnalyzer for creating the
PhraseQuery, but I suspect I shou
Andrzej Bialecki wrote:
Dennis Thrysøe wrote:
Andrzej Bialecki wrote:
What about using PhraseQuery, and store the path with all but first
path separator replaced by whitespace (i.e. "/foo bar baz one two
three"). Then you could query for "/foo bar", "/foo bar baz", and so
on...
Hi,
It doesn
Dennis Thrysøe wrote:
Andrzej Bialecki wrote:
What about using PhraseQuery, and store the path with all but first
path separator replaced by whitespace (i.e. "/foo bar baz one two
three"). Then you could query for "/foo bar", "/foo bar baz", and so
on...
Hi,
It doesn't seem to work though -
Andrzej Bialecki wrote:
What about using PhraseQuery, and store the path with all but first path
separator replaced by whitespace (i.e. "/foo bar baz one two three").
Then you could query for "/foo bar", "/foo bar baz", and so on...
Hi,
It doesn't seem to work though - unless I'm missing somethi
Andrzej Bialecki wrote:
What about using PhraseQuery, and store the path with all but first path
separator replaced by whitespace (i.e. "/foo bar baz one two three").
Then you could query for "/foo bar", "/foo bar baz", and so on...
That sounds like a really good suggestion. I'll try that. Thanks
Dennis Thrysøe wrote:
Hi,
The only alternative I can think of would be to store a whitespace
seperated list of all ancestors along with a document:
/foo /foo/bar /foo/bar/baz
But this has two drawbacks: Index storage space used, and the cost of
indexing (finding all ancestors).
So my question
Dennis Thrysøe wrote:
The only alternative I can think of would be to store a whitespace
seperated list of all ancestors along with a document:
/foo /foo/bar /foo/bar/baz
I think you will find that this kind of approach works very well (as it
has for me). But instead of adding one field named "p
Hi,
I'm seeking any kind of advice that I can find to solve a problem I've
run into with using lucene.
I'm integrating lucene as an alternative to other methods of indexing
and searching that already exist in our product. Therefore it would be
best if I could make the integration of lucene liv
11 matches
Mail list logo
