, 98, 105,
114, 97, 116, 101, 114, 111, 110]...', original message: bytes can be at most
32766 in length; got 95994
Please help to resolve this issue.
Any help to remove special characters from suggestion result will also work.
Thanks.
Abhay
Confidentiality Notice
===
: Hmm, setting -Dfile.encoding=UTF-8 solves the problem. I have to now check
: which component of the application screws it up, but at the moment I do NOT
: believe it is related to Solrj.
You can use the "forbidden-apis" project to analyze your code and look for
uses of APIs that depend on the
hi Jörn - something's decoding a UTF8 sequence using the legacy iso-8859-1
character set:
Jörn is J%C3%B6rn in UTF8
J%C3%B6rn misinterpreted as iso-8859-1 is Jörn
Jörn is J%C3%83%C2%B6rn in UTF8
I hope this helps track down the problem!
Andy
On Fri, 7 Aug 2020 at 12:08, Jörn Franke wrote:
>
Hmm, setting -Dfile.encoding=UTF-8 solves the problem. I have to now check
which component of the application screws it up, but at the moment I do NOT
believe it is related to Solrj.
On Fri, Aug 7, 2020 at 11:53 AM Jörn Franke wrote:
> Dear all,
>
> I have the following issues. I have a Solrj Cl
Dear all,
I have the following issues. I have a Solrj Client 8.6 (but it happens also
in previous versions), where I execute, for example, the following query:
Jörn
If I look into Solr Admin UI it finds all the right results.
If I use Solrj client then it does not find anything.
Further, investi
emad, I don't think its related to the field definition, rather looks
>> like
>>> an inherent bug. For the time being, I created a copyfield which uses a
>>> custom regex to remove whitespace and special characters and use it in
>> the
>>> function. I'll debug the source code and confirm if it's bug, will raise
>> a
>>> JIRA if needed.
>>>
>>>
>>>
>>> --
>>> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
>>
>>
> an inherent bug. For the time being, I created a copyfield which uses a
> > custom regex to remove whitespace and special characters and use it in
> the
> > function. I'll debug the source code and confirm if it's bug, will raise
> a
> > JIRA if needed.
> >
> >
> >
> > --
> > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
>
>
>
> > Ahemad, I don't think its related to the field definition, rather looks
> like
> > an inherent bug. For the time being, I created a copyfield which uses a
> > custom regex to remove whitespace and special characters and use it in
> the
> > func
Thanks Jan, I was not aware of this, appreciate your help.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
2019 kl. 18:51 skrev shamik :
>
> Ahemad, I don't think its related to the field definition, rather looks like
> an inherent bug. For the time being, I created a copyfield which uses a
> custom regex to remove whitespace and special characters and use it in the
> function. I&#
Ahemad, I don't think its related to the field definition, rather looks like
an inherent bug. For the time being, I created a copyfield which uses a
custom regex to remove whitespace and special characters and use it in the
function. I'll debug the source code and confirm if it's bu
Hi,Did you find any solution for this, I tried adding analyzers with keyword
tokenizer and reversewildcardfilterfactory but was not working.
It's working when I don't include spaces when I am doing wildcard search but
not giving the result when I have whitespaces and do wildcard search using *
I'm using Solr 7.5, here's the query:
q=line&fq=language:"english"&fq=Source2:("topicarticles"+OR+"sfdcarticles")&fl=url,title&bq=ADSKFeature:"CUI+(Command)"^7&bf=recip(ms(NOW/DAY,PublishDate),3.16e-11,1,1)^2+if(termfreq(ADSKFeature,'CUI
(Command)'),log(CaseCount),sqrt(CaseCount))&rows=10
--
Se
Hi Shamik,
String fieldType should keep the space. Can you give the full query that
you used when you get the error?
Also, which Solr version are you using?
Regards,
Edwin
On Wed, 27 Mar 2019 at 03:16, shamik wrote:
> Edwin,
>
>The field is a string type, here's the field definition.
>
>
Edwin,
The field is a string type, here's the field definition.
-Shamik
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi Shamik,
What fieldType are you using for the field that you are doing the function
queries on?
Regards,
Edwin
On Tue, 26 Mar 2019 at 06:40, Shamik Bandopadhyay wrote:
> Hi,
>
>I'm having trouble handling white space or special characters in
> function queries. Here&#x
Hi,
I'm having trouble handling white space or special characters in
function queries. Here's a sample function:
if(termfreq(ADSKFeature,'CUI (Command)'),log(CaseCount),sqrt(CaseCount))
I tried escaping the space with "\", but that didn't work either
t;nori" analyzer.
>
> Whether it's an error or an intentional question.
>
> All special characters are filtered.
>
> Special characters stored in the dictionary are also filtered.
>
> How do I print special characters?
>
>
Hi I'm using the "nori" analyzer.
Whether it's an error or an intentional question.
All special characters are filtered.
Special characters stored in the dictionary are also filtered.
How do I print special characters?
Hello Solr users,
I have a need to write a tokenizer for source code files in Solr, but don't
have the option of including custom JARs. So for ex:
Input: foo.bar
Tokens: 'foo', '.', 'bar'
How can I have a custom tokenizer or filter in schema.xml that can split on
some characters, but also not d
2018 10:39 PM, Rathor, Piyush (US - Philadelphia) wrote:
> > We are facing some issues in search with special characters. Can you
> please help in query if the search is done using following characters:
> >
> > • “&”
> > • AND
> > •
On 9/26/2018 10:39 PM, Rathor, Piyush (US - Philadelphia) wrote:
We are facing some issues in search with special characters. Can you please
help in query if the search is done using following characters:
• “&”
• AND
• (
• )
There are two
om> wrote:
> Hi All,
>
>
>
> We are facing some issues in search with special characters. Can you
> please help in query if the search is done using following characters:
>
> • “&”
>
>Example – Tata & Sons
>
Hi All,
We are facing some issues in search with special characters. Can you please
help in query if the search is done using following characters:
• “&”
Example – Tata & Sons
• AND
Example – Tata
Hi Shawn,
Yes I can confirm, it works with out any errors with multiple tokenizers.
Following is my analysis chain
StandardTokenizerFactory (only in index)
StopFilterFactory
LowerCaseFilterFactory
ASCIIFoldingFilterFactory
EnglishPossessiveFilterFactory
StemmerOverrideFilterFactory (only in query
(only in query)
> NgramTokenizerFactory (only in index)
>
> Regards,
> Lasitha
>
> On 18 Jul 2017 14:11, "Lasitha Wattaladeniya" wrote:
>
>> Hi devs,
>>
>> I have setup solr highlighting with default setup (only changed the
>> fragsize to 0 to
ly in index)
>
> Regards,
> Lasitha
>
> On 18 Jul 2017 14:11, "Lasitha Wattaladeniya" wrote:
>
>> Hi devs,
>>
>> I have setup solr highlighting with default setup (only changed the
>> fragsize to 0 to match any field length). It worked fine but
to match any field length). It worked fine but recently I
>> discovered it doesn't highlight for words with special characters in the
>> middle.
>>
>> For an example, let's say I have indexed email address test.f...@ran.com
>> to a ngram field. And when I search
(only in index)
Regards,
Lasitha
On 18 Jul 2017 14:11, "Lasitha Wattaladeniya" wrote:
> Hi devs,
>
> I have setup solr highlighting with default setup (only changed the
> fragsize to 0 to match any field length). It worked fine but recently I
> discovered it doesn't hi
Hi devs,
I have setup solr highlighting with default setup (only changed the
fragsize to 0 to match any field length). It worked fine but recently I
discovered it doesn't highlight for words with special characters in the
middle.
For an example, let's say I have indexed email addr
should not cause a problem for any
special characters.
My final query is:
{
limit : 10,
params:{
q.operators:"",
defType:"simple",
q:"${query}",
q.op:"${operator}",
qf:"${fields}",
indent:"off"
}
}
201
Hi,
I don't think dismax recognizes AND OR.
Special characters for dismax are + - and quotes.
In your example, ampersand may causing you trouble. Due to URL encode stuff...
Ahmet
On Sunday, January 29, 2017 12:17 AM, Jarosław Grązka
wrote:
Hi,
Reading Solr documentation about d
Hi,
Reading Solr documentation about dismax query
https://cwiki.apache.org/confluence/display/solr/The+DisMax+Query+Parser i
understood dismax query parser can interpret following special chars:
AND,OR,+,-,quotes (for phrases) and should ignore all others like
||,NOT,&&,~,^ etc and treat them as s
to actually preserve most of the ClassicTokenizerFactory functionality without
getting rid of leading special characters? The "Solr In Action" book (page 179)
claims that it is hard to extend the StandardTokenizerFactory. I'm assuming
this is the same for ClassicTokenizerFactory.
Thanks
-Andrew
lly preserve most of the ClassicTokenizerFactory functionality without
getting rid of leading special characters? The "Solr In Action" book (page 179)
claims that it is hard to extend the StandardTokenizerFactory. I'm assuming
this is the same for ClassicTokenizerFactory.
Thanks
-Andrew
g Lin Edwin Yeo <
>>> edwinye...@gmail.com> wrote:
>>>
>>>
>>> Yes, it throws the parse exception even if the query is properly escaped
>>> for ampersand (&) for defType=lucene.
>>>
>>> Should we treat this as a bug, and create
tion even if the query is properly escaped
for ampersand (&) for defType=lucene.
Should we treat this as a bug, and create a JIRA>
Regards,
Edwin
On 19 June 2016 at 08:07, Ahmet Arslan wrote:
If properly escaped ampersand throws parse exception, this could be a bug.
On Saturday, June 18
> On 19 June 2016 at 08:07, Ahmet Arslan wrote:
>
>
>
> If properly escaped ampersand throws parse exception, this could be a bug.
>
>
>
> On Saturday, June 18, 2016 7:12 PM, Zheng Lin Edwin Yeo <
> edwinye...@gmail.com> wrote:
> Hi,
>
> It does not w
.
What could be the reason that it did not work with the default
defType=lucene?
Regards,
Edwin
On 18 June 2016 at 01:04, Ahmet Arslan wrote:
> Hi,
>
> May be URL encoding issue?
> By the way, I would use back slash to escape special characters.
>
> Ahmet
>
> On Friday
:
> Hi,
>
> May be URL encoding issue?
> By the way, I would use back slash to escape special characters.
>
> Ahmet
>
> On Friday, June 17, 2016 10:08 AM, Zheng Lin Edwin Yeo <
> edwinye...@gmail.com> wrote:
>
>
>
> Hi,
>
> I encountered this error whe
Hi,
May be URL encoding issue?
By the way, I would use back slash to escape special characters.
Ahmet
On Friday, June 17, 2016 10:08 AM, Zheng Lin Edwin Yeo
wrote:
Hi,
I encountered this error when I tried to search with special characters,
like "&" and "#&quo
Hi,
I encountered this error when I tried to search with special characters,
like "&" and "#".
{
"responseHeader":{
"status":400,
"QTime":0},
"error":{
"msg":"org.apache.solr.search.SyntaxError: Canno
Hello,
I finally got it work: search for 5’ 3” (5 feet 3 inches)
It is strange for me that if I use WhitespaceTokenizer for field query-type
analyzer then it will receive only 5 and 3 with special characters removed.
It is also strange that EDisMax does not strips out odd number of quotes
tions
and you're using some of them whether you know it
or not as the schemas that come with Solr for fields like
text_general etc. are composed of some of these.
Best,
Erick
On Fri, Feb 12, 2016 at 2:02 AM, Modassar Ather wrote:
> These special characters can be removed if at begging or
These special characters can be removed if at begging or end or can be
taken care by the relevant filters depending on the schema defined.
E.g "Audit"/*Audit should be searched by query Audit so I see no reason of
indexing "/* of the content. You can use PatternReplaceFilter for
Thanks for quick response.
Should these be treated differently during index ?
I have tried *\"Audit* which is returning results of *Audit *also which is
incorrect. what do you say ?
On 12 February 2016 at 15:07, Modassar Ather wrote:
> You can search them by escaping with backslash.
>
> Best,
You can search them by escaping with backslash.
Best,
Modassar
HI,
How can we search special characters like *, " (double quote) where these
are actually solr uses for exact and wild card searches.
Please advice.
Regards,
Anil
; is a NOT operator
> >> and * is a wildcard. To get through the query parser, these (and a
> >> bunch of others, see below) must be escaped.
> >>
> >> Personally, though, I'd pre-scrub the data. Depending on your analysis
> >> chain such things may be
in such things may be thrown away anyway.
>>
>> https://cwiki.apache.org/confluence/display/solr/The+Standard+Query+Parser
>> - the "escaping special characters" bit.
>>
>> Best,
>> Erick
>>
>> On Thu, May 7, 2015 at 11:28 PM, Madhav Bahuguna
>&
ysis
> chain such things may be thrown away anyway.
>
> https://cwiki.apache.org/confluence/display/solr/The+Standard+Query+Parser
> - the "escaping special characters" bit.
>
> Best,
> Erick
>
> On Thu, May 7, 2015 at 11:28 PM, Madhav Bahuguna
> wrote:
> > S
#x27;d pre-scrub the data. Depending on your analysis
chain such things may be thrown away anyway.
https://cwiki.apache.org/confluence/display/solr/The+Standard+Query+Parser
- the "escaping special characters" bit.
Best,
Erick
On Thu, May 7, 2015 at 11:28 PM, Madhav Bahuguna
wrote:
>
ome,so second query is called to do a
fuzzy search.Now comes the problem my fuzzy query does not understand
special characters like +,-* which throws and error.If i dont pass special
characters it works fine. But in real world a user can put characters with
their search,which will throw an error.
Text search means searching of text, and special characters are not... text.
Why are you using the standard tokenizer if you are not trying to search
for standard text?
Try using the white space tokenizer, which will preserve special characters.
That said, the word delimiter filter will remove
not able to search on special characters like . ,_
my query
http://localhost:8983/solr/rna/select?q=name:"UAE
B"&wt=json&fl=name&rows=100
getting result UAE_bhdgsfsdbj
but for
http://localhost:8983/solr/rna/select?q=name:"UAE_"&wt=json&fl=name&rows=
Thanks for a quick response Jack.
Trying to escape it with a backslash, we also need to escape the whitespace. Is
that a default behavior while escaping special characters?
eg:
Search query: pcta \- all
No results returned
+(((name_starts_with:pcta^9.0 |
name_parts_starts_with:pcta^6.0
ginal Message-
From: Lanke,Aniruddha
Sent: Monday, October 13, 2014 11:03 AM
To: solr-user@lucene.apache.org
Subject: Re: eDisMax parser and special characters
Can the default behavior of "-" as a pre-fix operator be changed so it can
be searched as a string?
Thanks,
On Oct 9, 2
gt; Sent: Wednesday, October 8, 2014 4:38 PM
>> To: solr-user@lucene.apache.org
>> Subject: Re: eDisMax parser and special characters
>>
>> Sorry for a delayed reply here is more information -
>>
>> Schema that we are using - http://pastebin.com/WQAJCCp
; -Original Message- From: Lanke,Aniruddha
> Sent: Wednesday, October 8, 2014 4:38 PM
> To: solr-user@lucene.apache.org
> Subject: Re: eDisMax parser and special characters
>
> Sorry for a delayed reply here is more information -
>
> Schema that we are using - http://
again, so the hyphen gets
quoted, and then analyzed to nothing for text fields but is still a string
for string fields.
-- Jack Krupansky
-Original Message-
From: Lanke,Aniruddha
Sent: Wednesday, October 8, 2014 4:38 PM
To: solr-user@lucene.apache.org
Subject: Re: eDisMax parser an
Sorry for a delayed reply here is more information -
Schema that we are using - http://pastebin.com/WQAJCCph
Request Handler in config - http://pastebin.com/Y0kP40WF
Some analysis -
Search term: red -
Parser eDismax
No results show up
(+((DisjunctionMaxQuery((name_starts_with:red^9.0 |
name_par
There's not much information here.
What's the doc look like?
What is the analyzer chain for it?
What is the output when you add &debug=query?
Details matter. A lot ;)
Best,
Erick
On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner wrote:
> Try escaping special chars with a "\"
>
>
> On 10/08/2014 01
Try escaping special chars with a "\"
On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
We are using a eDisMax parser in our configuration. When we search using the
query term that has a ‘-‘ we don’t get any results back.
Search term: red - yellow
This doesn’t return any data back but
Max parser in our configuration. When we search using
> the query term that has a ‘-‘ we don’t get any results back.
>
> Search term: red - yellow
> This doesn’t return any data back but
>
> Search term: red yellow
> Will give back result ‘red - yellow’
>
> How does eDisMax tr
We are using a eDisMax parser in our configuration. When we search using the
query term that has a ‘-‘ we don’t get any results back.
Search term: red - yellow
This doesn’t return any data back but
Search term: red yellow
Will give back result ‘red - yellow’
How does eDisMax treat special
We are using a eDisMax parser in our configuration. When we search using the
query term that has a ‘-‘ we don’t get any results back.
Search term: red - yellow
This doesn’t return any data back but
Search term: red yellow
Will give back result ‘red - yellow’
How does eDisMax treat special
10:49 AM
To: solr-user@lucene.apache.org
Subject: Re: Exact match on string field with special characters
I may have provided too much background story for my question. What I am trying
to do at the core here, is an exact match on a single field. I do this
programmatically by reading the field v
Shoot I just noticed the error in my original post which would certainly
cause confusion.
Instead of
query.addFacetField(fq);
I meant to write
query.setParam("fq", fg);
Sorry.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Exact-match-on-string-field-wi
replacing double quotes and backslashes. I don't
strip special chars because I'm using the facet values for display. This
problem may be specific to SolrJ. Thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Exact-match-on-string-field-with-special-charact
string fields for faceting - to try to get an exact match. However, it
seems like to run a facet query I have to surround the value with double
quotes. That poses issues when the field value is
green "bath" towels
-or-
red \cars
Those two special characters must be transformed somehow o
ry, you can use
org.apache.solr.client.solrj.util.ClientUtils.escapeQueryChars().
-Michael
-Original Message-
From: tedsolr [mailto:tsm...@sciquest.com]
Sent: Wednesday, October 01, 2014 5:33 PM
To: solr-user@lucene.apache.org
Subject: Exact match on string field with special characters
I am trying to do SQL like aggregation (GROU
owels
-or-
red \cars
Those two special characters must be transformed somehow on indexing so I
can create the query:
(java)
...
String fg = fieldName + ":\"" + fieldValue + "\"";
query.addFacetField(fq);
...
Is there a way to request an exact match search without
To be honest, I'm not precisely sure what Google is really doing under the
hood since there is no detailed spec publically available. We know that
quotes do force a phrase searchin Google, but do they disable stemming or
preserve case and special characters? Unknown. Although, my PERCEPTI
non-tokenized fields will be one term, but for any tokenized fields
which split on white space, the phrase will be broken into separate tokens and
special characters will tend to be removed as well. The keyword tokenizer will
indeed treat the entire phrase as a single token, and the white space t
e term, but for any
tokenized fields which split on white space, the phrase will be broken into
separate tokens and special characters will tend to be removed as well. The
keyword tokenizer will indeed treat the entire phrase as a single token, and
the white space tokenizer will preserve specia
Hi all,
I have a docs that's indexed by text field with mention schema.
I have those docs names:
- Test host
- Test_host
- Test-host
- Test $host
When I'm trying to do exact search like: "test host"
All the results from above are shown as a results.
How c
Can someone help me out with this issue please?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search-term-having-special-characters-and-digits-tp4133385p4133770.html
Sent from the Solr - User mailing list archive at Nabble.com.
Thanks jack for prompt response!
So is there any solution to make this scenario works?
Or wildcard doesn't work with special characters and numerics?
Thanks,
G. Naresh Kumar
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search
Wildcard query only works for single terms. Any embedded special characters
will cause a term to be split into multiple terms at index time. The use of
a wildcard in a query term with embedded special characters will bypass
normal analysis - you need to enter the term exactly as it would be
Can some one please help me with this as I am struck with this issue..
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search-term-having-special-characters-and-digits-tp4133385p4133478.html
Sent from the Solr - User mailing list archive at
ldcard search and no didgits is returning results.
http://localhost:8080/solr/master/select?q=page_title_t:"an-*";
I have tried by adding WordDelimeter Filter but there is no luck.
Please suggest or guide how to make wildcard search works with special
characters and digits.
Appreciate i
t; Regards,Rohit
>
> > Date: Thu, 10 Apr 2014 08:44:36 -0700
> > From: iori...@yahoo.com
> > Subject: Re: Fails to index if unique field has special characters
> > To: solr-user@lucene.apache.org
> >
> > Hi Ayush,
> >
> > I thinks this
> &
Thanks, that was helpful.
Regards,Rohit
> Date: Thu, 10 Apr 2014 08:44:36 -0700
> From: iori...@yahoo.com
> Subject: Re: Fails to index if unique field has special characters
> To: solr-user@lucene.apache.org
>
> Hi Ayush,
>
> I thinks this
>
> ""I
Hi Ayush,
I thinks this
""IBM!12345". The exclamation mark ('!') is critical here, as it distinguishes
the prefix used to determine which shard to direct the document to."
https://cwiki.apache.org/confluence/display/solr/Shards+and+Indexing+Data+in+SolrCloud
On Thursday, April 10, 2014 2:3
Hi,
We are migrating from Solr 4.6 standalone to Solr 4.7 cloud version, while
reindexing the document we are getting the following error. This is happening
when the unique key has special character, this was not noticed in version 4.6
standalone mode, so we are not sure if this is a version pro
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121512.html
Sent from the Solr - User mailing list archive at Nabble.com.
the title i want as 1999/99.
Hope you get what i am trying to achieve. Is my understanding wrong
somewhere?
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121512.htm
Hi Kashish,
This is confusing. You gave the following example :
query 1999/99* should return RABIAN NIGHTS #01 (1999/99)
However you said "I cannot ignore parenthesis or other special characters..."
Above two contadicts each other.
Since you are after autocomplete you might be int
Hi, Pls help me with this.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121457.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi Erick,
I understand what you pointing out but the thing is.. this is for
autocomplete feature. I cannot ignore parenthesis or other special
characters as in certain titles like 'A Team of five', if the user fives 'a
team' then titles containing a-team and rest also comes o
s in autocomplete.
>
> Is there any best way to handle this? Or should i pass asterisk before and
> after the query?
>
> Thanks.
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4119678.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
-along-with-special-characters-tp4119608p4119678.html
Sent from the Solr - User mailing list archive at Nabble.com.
%2f99
I tried your way too. But no luck. :(
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4119615.html
Sent from the Solr - User mailing list archive at Nabble.com.
stopwords.txt" enablePositionIncrements="true" />
>
>
>
>
>
> words="stopwords.txt" enablePositionIncrements="true" />
>
>
>
>
>
>
> Please help we with this.
>
> Th
Hi Ahmet,
Thanks for your reply.
Yes. I pass my query this way - > q=title_autocomplete:1999%2f99
I tried your way too. But no luck. :(
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-spec
is my fieldType
Please help we with this.
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-alo
ng-if-the-query-conatins-numbers-along-with-special-characters-tp4119608.html
Sent from the Solr - User mailing list archive at Nabble.com.
That's a feature of the standard tokenizer. You'll have to use a field type
which uses the white space tokenizer to preserve special characters.
-- Jack Krupansky
-Original Message-
From: suren
Sent: Thursday, December 19, 2013 10:56 AM
To: solr-user@lucene.apache.org
Su
Unable to query strings ending with special characters, it is skipping the
last special character and giving the results. I am including the string in
double quotes.
For example i am unable to query strings like "JOHNSON &", "PEOPLES'".
It queries well for "JO
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/How-to-escape-special-characters-from-SOLR-response-header-tp4100772.html
> Sent from the Solr - User mailing list archive at Nabble.com.
1 - 100 of 272 matches
Mail list logo
