: I do not believe the SOLR or LUCENE syntax allows this
At the lowest level, Solr and Lucene-Java both support any arbitrary
character you want in the field name -- it's just that sevearl features
use syntax that doesn't play nicely with characters like whitespace in
field names.
when using t
-
> EARTH has a Right To Life,
> otherwise we all die.
>
> Read 'Hot, Flat, and Crowded'
> Laugh at http://www.yert.com/film.php
>
>
> --- On Mon, 3/8/10, Israel Ekpo wrote:
>
> > From: Israel Ekpo
> > Subject: Re: Search on dynamic fields w
'Hot, Flat, and Crowded'
Laugh at http://www.yert.com/film.php
--- On Mon, 3/8/10, Israel Ekpo wrote:
> From: Israel Ekpo
> Subject: Re: Search on dynamic fields which contains spaces /special
> characters
> To: solr-user@lucene.apache.org
> Date: Monday, March 8, 20
I do not believe the SOLR or LUCENE syntax allows this
You need to get rid of all the spaces in the field name
If not, then you will be searching for "short" in the default field and then
"name1" in the "name" field.
http://wiki.apache.org/solr/SolrQuerySyntax
http://lucene.apache.org/java/2_9_
I'm 100% sure about that :)
On Jun 5, 2009, at 9:05 PM, Avlesh Singh wrote:
My bad! Please ignore the previous reply.
I just read your mail again to realize that there is a problem.
Are you sure that the case (upper/lower) in your query and index
match? Any
difference in cases would not fetc
My bad! Please ignore the previous reply.
I just read your mail again to realize that there is a problem.
Are you sure that the case (upper/lower) in your query and index match? Any
difference in cases would not fetch you results for a field of type string.
Cheers
Avlesh
On Sat, Jun 6, 2009 at 1
>
> When I search for exact match on "New" I get zero results!
> q=17000219_s:New
> But when I search on 1003356 I get results! q=17000219_s: 1003356
> And when I use wildcards I get results too! q=17000219_s: *New or
> q=17000219_s:New* or q=17000219_s:*New*
>
Nothing your case is unexpected, R
