cancel
Showing results for 
Search instead for 
Did you mean: 

Lucene performance/wildcard searches not working

dbevacqua
Champ in-the-making
Champ in-the-making
we have a repo with about 400k nodes and 2.8M properties. A a very simple search on the lucene index for

@cms\:name:research

is taking over half an hour to complete (I have not actually bothered to let it finish). There will be tens of thousands of matches (searches for more obscure words are taking of order 1s). In the wiki & forums there are a number of references to being able to limit the number of results, but I can't find how to do it. Could you tell me?

The other thing is that wildcard searches do not seem to be working, so

@cms\:name:nanotechnology

gives some results, but

@cms\:name:nano
@cms\:name:nano*
@cms\:name:"nano*"
@cms\:name:"nano"*
etc

do not.

Any ideas?

Thanks,

Dominic
11 REPLIES 11

dbevacqua
Champ in-the-making
Champ in-the-making
found this note in the javadoc for ResultSetRow:

TODO: Support for other non attribute features such as parents and path

So I guess that answers my question  Smiley Happy

I'm guessing it's not that hard to do. Will look into having a go myself.

Dominic

dbevacqua
Champ in-the-making
Champ in-the-making
got this working… sort of. See http://forums.alfresco.com/viewtopic.php?p=12723#12723.

Dominic