You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by gateway0 <re...@yahoo.de> on 2009/08/03 01:30:19 UTC
Solr failing on "y" charakter in string?
Hi,
I have the following setting:
schema.xml:
"<field name="kunde" type="text" indexed="true" stored="true" />"
the "text" field-type was updated with the "preserveOriginal=1" option in
the schema
I have the following string indexd in the field "kunde"
"Harry Heim KG"
Now when I search for "kunde:harry*" it gives me an empty result.
When I search for "kunde:harry" I get the right result. Also "kunde:harr*"
works just fine.
The strange thing is that with every other string (for example
"kunde:heim*") I will get the right result.
So why not on "harry*" with an "y*" at the end?
kind regards, S.
--
View this message in context: http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24783211.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: When to optimize?
Posted by Matt Weber <ma...@mattweber.org>.
I would say once a day is a pretty good rule of thumb. If you think
this is a bit much and if you have few updates you can probably back
that off to once every couple days to once a week. However, if you
have a large batch update or your query performance starts to degrade,
you will need to optimize your index.
Thanks,
Matt Weber
On Sep 13, 2009, at 6:21 PM, William Pierce wrote:
> Folks:
>
> Are there good rules of thumb for when to optimize? We have a large
> index consisting of approx 7M documents and we currently have it set
> to optimize once a day. But sometimes there are very few changes
> that have been committed during a day and it seems like a waste to
> optimize (esp. since our servers are pretty well loaded).
>
> So I was looking to get some good rules of thumb for when it makes
> sense to optimize: Optimize when x% of the documents have been
> changed since the last optimize or some such.
>
> Any ideas would be greatly appreciated!
>
> -- Bill
When to optimize?
Posted by William Pierce <ev...@hotmail.com>.
Folks:
Are there good rules of thumb for when to optimize? We have a large index
consisting of approx 7M documents and we currently have it set to optimize
once a day. But sometimes there are very few changes that have been
committed during a day and it seems like a waste to optimize (esp. since our
servers are pretty well loaded).
So I was looking to get some good rules of thumb for when it makes sense to
optimize: Optimize when x% of the documents have been changed since the
last optimize or some such.
Any ideas would be greatly appreciated!
-- Bill
Re: Advice on updating solr indexes
Posted by Lance Norskog <go...@gmail.com>.
There is a special-purpose feature that solves exactly this problem: it
assigns the score for a particular field from a file which contains every
known value of the field and a matching float.
Doing a quick scan of the code, this seems to be how it works: the
declaration of the field in schema.xml contains the fact that its score is
derived from an external file. It can only be done on fields defined 'float'
(not 'sfloat'). Each query may give a file name and the field name. This
file should be sorted by the values of the field. It will be loaded and
cached and a future query may give only the field name.
Again, this description may not be completely right. (The float/sfloat thing
might be wrong, for example.) The parameters for this feature are buried in
the Solr source. There is no mention of this feature in the wiki.
The files are:
http://svn.apache.org/repos/asf/lucene/solr/trunk/src/java/org/apache/solr/search/function/FileFloatSource.java
and
http://svn.apache.org/repos/asf/lucene/solr/trunk/src/java/org/apache/solr/schema/ExternalFileField.java
I have not tried any of this. Should you try this feature and get it
working, please document it on the wiki :) Also, if there are any bugs or
gotchas, please post a Jira issue.
--
Lance Norskog
goksron@gmail.com
On Sat, Aug 15, 2009 at 7:38 AM, William Pierce <ev...@hotmail.com>wrote:
> Folks:
>
> In our app we index approx 50 M documents every so often. One of the
> fields in each document is called "CompScore" which is a score that our
> back-end computes for each document. The computation of this score is
> heavy-weight and is done only approximately once every few days. When
> documents are retrieved during a search we return results sorted by the Solr
> score first and then the CompScore.
>
> The issue we have this: Every week or so when the back-end routines run to
> compute "CompScore" we need to delete and insert these 50 M documents into
> the index. This happens even though the a majority of the documents have
> not changed.
>
> I think there is no way in Solr to simply update a field in the index.
>
> If others have encountered a similar issue, I'd be interested in hearing
> about their solutions!
>
> Best,
>
> - Bill
>
Advice on updating solr indexes
Posted by William Pierce <ev...@hotmail.com>.
Folks:
In our app we index approx 50 M documents every so often. One of the fields
in each document is called "CompScore" which is a score that our back-end
computes for each document. The computation of this score is heavy-weight
and is done only approximately once every few days. When documents are
retrieved during a search we return results sorted by the Solr score first
and then the CompScore.
The issue we have this: Every week or so when the back-end routines run to
compute "CompScore" we need to delete and insert these 50 M documents into
the index. This happens even though the a majority of the documents have
not changed.
I think there is no way in Solr to simply update a field in the index.
If others have encountered a similar issue, I'd be interested in hearing
about their solutions!
Best,
- Bill
Re: Solr failing on "y" charakter in string?
Posted by Avlesh Singh <av...@gmail.com>.
>
> I have a Solr text field and when I use Solr's field analysis tool, it
> shows that wildcard queries are being stemmed. But query results indicate
> that it is not. It looks like there is a bug in the tool.
>
I am in agreement. Seems like a bug to me.
Cheers
Avlesh
On Mon, Aug 3, 2009 at 10:19 PM, Bill Au <bi...@gmail.com> wrote:
> I have a Solr text field and when I use Solr's field analysis tool, it
> shows
> that wildcard queries are being stemmed. But query results indicate that
> it
> is not. It looks like there is a bug in the tool.
>
> Bill
>
> On Mon, Aug 3, 2009 at 7:21 AM, gateway0 <re...@yahoo.de> wrote:
>
> >
> > Ok thanks you´re right.
> >
> > But the thing is my users will often search for expressions like: "Harr"
> or
> > "har" etc..
> >
> > So I thought I automatically add the wildcard "*" to every request.
> >
> > If that too gets me into trouble "Harr*"=>no result "harry*"=>no result
> >
> > What should I do?
> >
> >
> >
> > Otis Gospodnetic wrote:
> > >
> > > I believe it's because wildcard queries are not stemmed. During
> indexing
> > > "harry" probably got stemmed to "harr", so now "harry*" doesn't match,
> > > because there is no "harry" token in that string, only "harr". Why
> > > wildcard queries are not analyzed is described in the Lucene FAQ on the
> > > Lucene Wiki.
> > >
> > > You could also try searching for kunde:Harr* for example (not the
> > > upper-case Harr). I bet it won't result in a hit for the same reason -
> > at
> > > index time you probably lower-case tokens with
> LowerCaseFilter(Factory),
> > > and if you search for Harr*, the lower-casing won't happen because the
> > > query string with the wildcard character isn't analyzed.
> > >
> > > Otis
> > > --
> > > Sematext is hiring -- http://sematext.com/about/jobs.html?mls
> > > Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
> > >
> > >
> > >
> > > ----- Original Message ----
> > >> From: gateway0 <re...@yahoo.de>
> > >> To: solr-user@lucene.apache.org
> > >> Sent: Sunday, August 2, 2009 7:30:19 PM
> > >> Subject: Solr failing on "y" charakter in string?
> > >>
> > >>
> > >> Hi,
> > >>
> > >> I have the following setting:
> > >> schema.xml:
> > >> ""
> > >> the "text" field-type was updated with the "preserveOriginal=1" option
> > in
> > >> the schema
> > >>
> > >> I have the following string indexd in the field "kunde"
> > >> "Harry Heim KG"
> > >>
> > >> Now when I search for "kunde:harry*" it gives me an empty result.
> > >>
> > >> When I search for "kunde:harry" I get the right result. Also
> > >> "kunde:harr*"
> > >> works just fine.
> > >>
> > >> The strange thing is that with every other string (for example
> > >> "kunde:heim*") I will get the right result.
> > >>
> > >> So why not on "harry*" with an "y*" at the end?
> > >>
> > >> kind regards, S.
> > >> --
> > >> View this message in context:
> > >>
> >
> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24783211.html
> > >> Sent from the Solr - User mailing list archive at Nabble.com.
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> >
> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24789070.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
> >
> >
>
Re: Solr failing on "y" charakter in string?
Posted by Bill Au <bi...@gmail.com>.
I have a Solr text field and when I use Solr's field analysis tool, it shows
that wildcard queries are being stemmed. But query results indicate that it
is not. It looks like there is a bug in the tool.
Bill
On Mon, Aug 3, 2009 at 7:21 AM, gateway0 <re...@yahoo.de> wrote:
>
> Ok thanks you´re right.
>
> But the thing is my users will often search for expressions like: "Harr" or
> "har" etc..
>
> So I thought I automatically add the wildcard "*" to every request.
>
> If that too gets me into trouble "Harr*"=>no result "harry*"=>no result
>
> What should I do?
>
>
>
> Otis Gospodnetic wrote:
> >
> > I believe it's because wildcard queries are not stemmed. During indexing
> > "harry" probably got stemmed to "harr", so now "harry*" doesn't match,
> > because there is no "harry" token in that string, only "harr". Why
> > wildcard queries are not analyzed is described in the Lucene FAQ on the
> > Lucene Wiki.
> >
> > You could also try searching for kunde:Harr* for example (not the
> > upper-case Harr). I bet it won't result in a hit for the same reason -
> at
> > index time you probably lower-case tokens with LowerCaseFilter(Factory),
> > and if you search for Harr*, the lower-casing won't happen because the
> > query string with the wildcard character isn't analyzed.
> >
> > Otis
> > --
> > Sematext is hiring -- http://sematext.com/about/jobs.html?mls
> > Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
> >
> >
> >
> > ----- Original Message ----
> >> From: gateway0 <re...@yahoo.de>
> >> To: solr-user@lucene.apache.org
> >> Sent: Sunday, August 2, 2009 7:30:19 PM
> >> Subject: Solr failing on "y" charakter in string?
> >>
> >>
> >> Hi,
> >>
> >> I have the following setting:
> >> schema.xml:
> >> ""
> >> the "text" field-type was updated with the "preserveOriginal=1" option
> in
> >> the schema
> >>
> >> I have the following string indexd in the field "kunde"
> >> "Harry Heim KG"
> >>
> >> Now when I search for "kunde:harry*" it gives me an empty result.
> >>
> >> When I search for "kunde:harry" I get the right result. Also
> >> "kunde:harr*"
> >> works just fine.
> >>
> >> The strange thing is that with every other string (for example
> >> "kunde:heim*") I will get the right result.
> >>
> >> So why not on "harry*" with an "y*" at the end?
> >>
> >> kind regards, S.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24783211.html
> >> Sent from the Solr - User mailing list archive at Nabble.com.
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24789070.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
RE: Solr failing on "y" charakter in string?
Posted by Ensdorf Ken <En...@zoominfo.com>.
> Ok still not working with new field "text_two":
> "<str name="q">text:"Har*" text_two:"Har*"</str>"
> ==> result 0
>
> Schema Updates:
> "
> <fieldType name="text_two" class="solr.TextField"
> positionIncrementGap="100">
> <analyzer type="index">
> <tokenizer class="solr.LowerCaseTokenizerFactory"/>
> <filter class="solr.LowerCaseFilterFactory"/>
> </analyzer>
> <analyzer type="query">
> <tokenizer class="solr.LowerCaseTokenizerFactory"/>
> <filter class="solr.LowerCaseFilterFactory"/>
> </analyzer>
> </fieldType>
>
>
> <field name="text_two" type="text_two" indexed="true" stored="false"
> multiValued="true"/>
>
> <copyField source="text" dest="text_two"/>
> "
I'm pretty sure the query string needs to be lower-case, since a wildcard query is not analyzed.
I think what Avlesh was suggesting was more like this:
"<str name="q">text:"Har" text_two:"har*"</str>"
So the original field would be for a regular query containing whatever the user entered and would undergo the usual analysis for searching, and the secondary field would be used to construct a wildcard query which would strictly serve the "begins-with" case.
-Ken
Re: Solr failing on "y" charakter in string?
Posted by gateway0 <re...@yahoo.de>.
Ok still not working with new field "text_two":
"<str name="q">text:"Har*" text_two:"Har*"</str>"
==> result 0
Schema Updates:
"
<fieldType name="text_two" class="solr.TextField"
positionIncrementGap="100">
<analyzer type="index">
<tokenizer class="solr.LowerCaseTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
<analyzer type="query">
<tokenizer class="solr.LowerCaseTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
</fieldType>
<field name="text_two" type="text_two" indexed="true" stored="false"
multiValued="true"/>
<copyField source="text" dest="text_two"/>
"
This is what you suggested, right?
kind regards, S.
Avlesh Singh wrote:
>
> The easiest thing to do would be to create a new field in your schema
> which
> only has a lowercasefilter applied to it. While searching perform searches
> across the two fields. You'll get desired results.
>
> You can use the <copyField> directive in your schema.xml for copying data
> from your original field into the new field.
>
> Cheers
> Avlesh
>
> On Mon, Aug 3, 2009 at 4:51 PM, gateway0 <re...@yahoo.de> wrote:
>
>>
>> Ok thanks you´re right.
>>
>> But the thing is my users will often search for expressions like: "Harr"
>> or
>> "har" etc..
>>
>> So I thought I automatically add the wildcard "*" to every request.
>>
>> If that too gets me into trouble "Harr*"=>no result "harry*"=>no result
>>
>> What should I do?
>>
>>
>>
>> Otis Gospodnetic wrote:
>> >
>> > I believe it's because wildcard queries are not stemmed. During
>> indexing
>> > "harry" probably got stemmed to "harr", so now "harry*" doesn't match,
>> > because there is no "harry" token in that string, only "harr". Why
>> > wildcard queries are not analyzed is described in the Lucene FAQ on the
>> > Lucene Wiki.
>> >
>> > You could also try searching for kunde:Harr* for example (not the
>> > upper-case Harr). I bet it won't result in a hit for the same reason -
>> at
>> > index time you probably lower-case tokens with
>> LowerCaseFilter(Factory),
>> > and if you search for Harr*, the lower-casing won't happen because the
>> > query string with the wildcard character isn't analyzed.
>> >
>> > Otis
>> > --
>> > Sematext is hiring -- http://sematext.com/about/jobs.html?mls
>> > Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
>> >
>> >
>> >
>> > ----- Original Message ----
>> >> From: gateway0 <re...@yahoo.de>
>> >> To: solr-user@lucene.apache.org
>> >> Sent: Sunday, August 2, 2009 7:30:19 PM
>> >> Subject: Solr failing on "y" charakter in string?
>> >>
>> >>
>> >> Hi,
>> >>
>> >> I have the following setting:
>> >> schema.xml:
>> >> ""
>> >> the "text" field-type was updated with the "preserveOriginal=1" option
>> in
>> >> the schema
>> >>
>> >> I have the following string indexd in the field "kunde"
>> >> "Harry Heim KG"
>> >>
>> >> Now when I search for "kunde:harry*" it gives me an empty result.
>> >>
>> >> When I search for "kunde:harry" I get the right result. Also
>> >> "kunde:harr*"
>> >> works just fine.
>> >>
>> >> The strange thing is that with every other string (for example
>> >> "kunde:heim*") I will get the right result.
>> >>
>> >> So why not on "harry*" with an "y*" at the end?
>> >>
>> >> kind regards, S.
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24783211.html
>> >> Sent from the Solr - User mailing list archive at Nabble.com.
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24789070.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24790836.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr failing on "y" charakter in string?
Posted by Avlesh Singh <av...@gmail.com>.
The easiest thing to do would be to create a new field in your schema which
only has a lowercasefilter applied to it. While searching perform searches
across the two fields. You'll get desired results.
You can use the <copyField> directive in your schema.xml for copying data
from your original field into the new field.
Cheers
Avlesh
On Mon, Aug 3, 2009 at 4:51 PM, gateway0 <re...@yahoo.de> wrote:
>
> Ok thanks you´re right.
>
> But the thing is my users will often search for expressions like: "Harr" or
> "har" etc..
>
> So I thought I automatically add the wildcard "*" to every request.
>
> If that too gets me into trouble "Harr*"=>no result "harry*"=>no result
>
> What should I do?
>
>
>
> Otis Gospodnetic wrote:
> >
> > I believe it's because wildcard queries are not stemmed. During indexing
> > "harry" probably got stemmed to "harr", so now "harry*" doesn't match,
> > because there is no "harry" token in that string, only "harr". Why
> > wildcard queries are not analyzed is described in the Lucene FAQ on the
> > Lucene Wiki.
> >
> > You could also try searching for kunde:Harr* for example (not the
> > upper-case Harr). I bet it won't result in a hit for the same reason -
> at
> > index time you probably lower-case tokens with LowerCaseFilter(Factory),
> > and if you search for Harr*, the lower-casing won't happen because the
> > query string with the wildcard character isn't analyzed.
> >
> > Otis
> > --
> > Sematext is hiring -- http://sematext.com/about/jobs.html?mls
> > Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
> >
> >
> >
> > ----- Original Message ----
> >> From: gateway0 <re...@yahoo.de>
> >> To: solr-user@lucene.apache.org
> >> Sent: Sunday, August 2, 2009 7:30:19 PM
> >> Subject: Solr failing on "y" charakter in string?
> >>
> >>
> >> Hi,
> >>
> >> I have the following setting:
> >> schema.xml:
> >> ""
> >> the "text" field-type was updated with the "preserveOriginal=1" option
> in
> >> the schema
> >>
> >> I have the following string indexd in the field "kunde"
> >> "Harry Heim KG"
> >>
> >> Now when I search for "kunde:harry*" it gives me an empty result.
> >>
> >> When I search for "kunde:harry" I get the right result. Also
> >> "kunde:harr*"
> >> works just fine.
> >>
> >> The strange thing is that with every other string (for example
> >> "kunde:heim*") I will get the right result.
> >>
> >> So why not on "harry*" with an "y*" at the end?
> >>
> >> kind regards, S.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24783211.html
> >> Sent from the Solr - User mailing list archive at Nabble.com.
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24789070.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
Re: Solr failing on "y" charakter in string?
Posted by gateway0 <re...@yahoo.de>.
Ok thanks you´re right.
But the thing is my users will often search for expressions like: "Harr" or
"har" etc..
So I thought I automatically add the wildcard "*" to every request.
If that too gets me into trouble "Harr*"=>no result "harry*"=>no result
What should I do?
Otis Gospodnetic wrote:
>
> I believe it's because wildcard queries are not stemmed. During indexing
> "harry" probably got stemmed to "harr", so now "harry*" doesn't match,
> because there is no "harry" token in that string, only "harr". Why
> wildcard queries are not analyzed is described in the Lucene FAQ on the
> Lucene Wiki.
>
> You could also try searching for kunde:Harr* for example (not the
> upper-case Harr). I bet it won't result in a hit for the same reason - at
> index time you probably lower-case tokens with LowerCaseFilter(Factory),
> and if you search for Harr*, the lower-casing won't happen because the
> query string with the wildcard character isn't analyzed.
>
> Otis
> --
> Sematext is hiring -- http://sematext.com/about/jobs.html?mls
> Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
>
>
>
> ----- Original Message ----
>> From: gateway0 <re...@yahoo.de>
>> To: solr-user@lucene.apache.org
>> Sent: Sunday, August 2, 2009 7:30:19 PM
>> Subject: Solr failing on "y" charakter in string?
>>
>>
>> Hi,
>>
>> I have the following setting:
>> schema.xml:
>> ""
>> the "text" field-type was updated with the "preserveOriginal=1" option in
>> the schema
>>
>> I have the following string indexd in the field "kunde"
>> "Harry Heim KG"
>>
>> Now when I search for "kunde:harry*" it gives me an empty result.
>>
>> When I search for "kunde:harry" I get the right result. Also
>> "kunde:harr*"
>> works just fine.
>>
>> The strange thing is that with every other string (for example
>> "kunde:heim*") I will get the right result.
>>
>> So why not on "harry*" with an "y*" at the end?
>>
>> kind regards, S.
>> --
>> View this message in context:
>> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24783211.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24789070.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr failing on "y" charakter in string?
Posted by Otis Gospodnetic <ot...@yahoo.com>.
I believe it's because wildcard queries are not stemmed. During indexing "harry" probably got stemmed to "harr", so now "harry*" doesn't match, because there is no "harry" token in that string, only "harr". Why wildcard queries are not analyzed is described in the Lucene FAQ on the Lucene Wiki.
You could also try searching for kunde:Harr* for example (not the upper-case Harr). I bet it won't result in a hit for the same reason - at index time you probably lower-case tokens with LowerCaseFilter(Factory), and if you search for Harr*, the lower-casing won't happen because the query string with the wildcard character isn't analyzed.
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
----- Original Message ----
> From: gateway0 <re...@yahoo.de>
> To: solr-user@lucene.apache.org
> Sent: Sunday, August 2, 2009 7:30:19 PM
> Subject: Solr failing on "y" charakter in string?
>
>
> Hi,
>
> I have the following setting:
> schema.xml:
> ""
> the "text" field-type was updated with the "preserveOriginal=1" option in
> the schema
>
> I have the following string indexd in the field "kunde"
> "Harry Heim KG"
>
> Now when I search for "kunde:harry*" it gives me an empty result.
>
> When I search for "kunde:harry" I get the right result. Also "kunde:harr*"
> works just fine.
>
> The strange thing is that with every other string (for example
> "kunde:heim*") I will get the right result.
>
> So why not on "harry*" with an "y*" at the end?
>
> kind regards, S.
> --
> View this message in context:
> http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24783211.html
> Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr failing on "y" charakter in string?
Posted by gateway0 <re...@yahoo.de>.
Ok still not working with new field "text_two":
"<str name="q">text:"Har*" text_two:"Har*"</str>"
==> result 0
Schema Updates:
"
<fieldType name="text_two" class="solr.TextField"
positionIncrementGap="100">
<analyzer type="index">
<tokenizer class="solr.LowerCaseTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
<analyzer type="query">
<tokenizer class="solr.LowerCaseTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
</fieldType>
<field name="text_two" type="text_two" indexed="true" stored="false"
multiValued="true"/>
<copyField source="text" dest="text_two"/>
"
This is what you suggested, right?
kind regards, S.
gateway0 wrote:
>
> Hi,
>
> I have the following setting:
> schema.xml:
> "<field name="kunde" type="text" indexed="true" stored="true" />"
> the "text" field-type was updated with the "preserveOriginal=1" option in
> the schema
>
> I have the following string indexd in the field "kunde"
> "Harry Heim KG"
>
> Now when I search for "kunde:harry*" it gives me an empty result.
>
> When I search for "kunde:harry" I get the right result. Also "kunde:harr*"
> works just fine.
>
> The strange thing is that with every other string (for example
> "kunde:heim*") I will get the right result.
>
> So why not on "harry*" with an "y*" at the end?
>
> kind regards, S.
>
--
View this message in context: http://www.nabble.com/Solr-failing-on-%22y%22-charakter-in-string--tp24783211p24790774.html
Sent from the Solr - User mailing list archive at Nabble.com.