Restriction: No "*" (wildcard) at the beginning of a search phrase.

Added by Mark Schlieker 1110 days ago

Hello,

SupoSE can not only search for a file name inside a SVN repository but also for many other items. This is possible because it makes use of "fields". There is also a field "contents" which shall probably enable the user to search the contents of a file, right?
The problem is that SupoSE doesnt allow me to use a wildcard at the beginning of the search phrase. This restriction might come from "Lucene", a component used for implementing the search indexer and query interface. But with this restriction I feel SupoSE's usage is very limited or do you have an idea to solve or work around this problem?

How for example would I phrase the search query to make SupoSE find all documents which have the word "draft" in their file name and "John Doe" occuring at least once in its contents?

This might also require to phrase search terms as combined words as I dont like to find documents which might only contain "John Something" and "Something Doe".

How is the planning for the future?
I really like SupoSE and I hope it will soon reach a state as standard tool for Subversion.

Sincerely,
Mark


Replies

RE: Restriction: No "*" (wildcard) at the beginning of a search phrase. - Added by Karl Heinz Marbaise 1108 days ago

Hello Mark,

SupoSE can not only search for a file name inside a SVN repository but also for many other items. This is possible because it makes use of "fields". There is also a field "contents" which shall probably enable the user to search the contents of a file, right?

Yes this is the exact intention of this field.

The problem is that SupoSE doesnt allow me to use a wildcard at the beginning of the search phrase.

Yeah...this was in relationship with the older versions of Lucene and my lack of implementing it...

This restriction might come from "Lucene", a component used for implementing the search indexer and query interface. But with this restriction I feel SupoSE's usage is very limited or do you have an idea to solve or work around this problem?

That was my thought too, cause e.g. for filenames it is not a such good way ...
It is simpler to say things like this:
--query "+filename:*log4j*"
--query "+filename:*.java"

The above is already working the development version. There are some problems with upper-case/lower-case things but many things are working...

How for example would I phrase the search query to make SupoSE find all documents which have the word "draft" in their file name and "John Doe" occuring at least once in its contents?

The result should be a simple thing like this:
--query "+filename:*draft* +contents:\"John Doe\""I'm currently not sure about the quoting, but this kind should be the result of such a query. I have to think about the quoting problem.

This might also require to phrase search terms as combined words as I dont like to find documents which might only contain "John Something" and "Something Doe".

Of course not.

How is the planning for the future?

To solve this kind of requirements...or to be more precisely many of them are already solved in the current development version...

I really like SupoSE and I hope it will soon reach a state as standard tool for Subversion.

Thanks for the honour ;-)

What do you think about a new release within a few days ?

Kind regards
Karl Heinz Marbaise

RE: Restriction: No "*" (wildcard) at the beginning of a search phrase. - Added by Karl Heinz Marbaise 1108 days ago

Hi Mark,

i have decided to distribute a new release 0.5.2 today. Take a look into the files area and check if this meets your requirements or if you find some problems don't hesitate to write them into the issue tracking system or into the forum.

Kind regards
Karl Heinz Marbaise