I'd recommend that you spend some time with the
admin/analysis page.
KeywordTokenizer doesn't break up the input at _all_. So
the text "this is a black cat" will never match anything that
starts out "black". String is even more restrictive, it not only doesn't
tokenize, it won't allow lower case.
On solr3.6 search while giving query "black\ cat*"(as you mentioned in post),
I am not getting any result.
Instead of "black\ cat*" if I am querying "black*\ cat*", its giving result
as
black forest cat
black cat
black color cat.
But I need only these type result i.e.
black cat
black cat is beaut
Right, this is a quirk of phrase queries. For wildcards to work in phrase
queries you need SOLR-1604 (ComplexPhraseQueryParser).
Or you need to escape your spaces, i.e.
black\ cat*
Best,
Erick
On Tue, Aug 5, 2014 at 11:09 PM, zameer wrote:
> If we search only "black*" it works but when we use
If we search only "black*" it works but when we use search text "black cat*"
or "(black cat)*" or "(black cat*)*" it come blank.
Thank you in advance
--
View this message in context:
http://lucene.472066.n3.nabble.com/matching-starts-with-only-tp4094430p4
Be aware that the string type is not analyzed in any way,
so your searches are case sensitive. There's a "lowercase"
type in the example schema.xml that combines
KeywordTokenizer with LowercaseFilter for case-insensitive
searches that you might find useful.
Besides regex, this might be a good plac
I've changed the field name to string type, the default one presented in
schema.xml, and I got what I needed.
thanks for your time.
--
View this message in context:
http://lucene.472066.n3.nabble.com/matching-starts-with-only-tp4094430p4094637.html
Sent from the Solr - User mailing list archi
search by "starts with" is something new I have to add, as well as the data I
have to index for this purpose, so it's ok to create a new field.
But once I added the following field type:
And:
indexing, and afterwards searching
On 10/9/2013 2:16 PM, adm1n wrote:
Why this field have to be copyField? Couldn't it be a single field, for
I always assume that people already are using the existing field and
type for other purposes. Offering advice without making that assumption
will usually result in people making a chang
Shawn Heisey-4:
thanks for the quick response.
Why this field have to be copyField? Couldn't it be a single field, for
example:
thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/matching-start
On 10/9/2013 12:57 PM, adm1n wrote:
My index contains documents which could be a single word or a short sentence
which contains up to 4-5 words. I need to return documents, which "starts
with" only from the searched pattern.
in regex it would be [^my_query].
for example, for a docs:
black
beaut
10 matches
Mail list logo
