Hi Thomas,
I think one solution would be similar to the autocomplete function I've
implemented in solr, you can use this as follows in solr:
FieldType:
This can then match on the whole string OR part of the string. To use
the QueryParser, you'd not be using the query part of the ana
Btw. I tried the wildcard since I found something on google, which noted
wildcards together with StartsWith queries.
Thomas Becker wrote:
Hi Ian,
no the wild cards should not be necessary. That was just the last try
out of some. I now the exact content of both fields in my range query.
The c
Hi Ian,
no the wild cards should not be necessary. That was just the last try
out of some. I now the exact content of both fields in my range query.
The case is as the java code found it, but the analyzer will lowercase
it anyhow. I'm trying the SimpleAnalyzer since all other seem to ommit
si
Hi
Are you sure your range queries should have wild card asterisks on the
end? Looks odd to me and I don't know what the effect would be.
I'd also prefer everything in lower case but maybe you've got the
right analyzers being used consistently in indexing and searching
chains.
--
Ian.
On F
Hi all,
I need to replace some db queries with lucene due to response time
issues for sure. In this special case I need to do a range query on a
field and a prefix query. I'm trying to prepare and try my query in luke
with no success before migrating it to java.
I need to find all names star
