You are absolutely right. The fields have trailing spaces in it. Thanks Erick
for your time. Really appreciated!
Thanks,
Alex
On May 12, 2010, at 8:29 PM, Erick Erickson wrote:
> Click the "schema browser" link on the admin page.
> On the next page click
> the "fields" link, then the field in
Found the problem! It's because all the values in productType field have
trailing spaces in it like this: "ProductBean ". Thanks Hoss for your
suggestion of using Luke query which exposed the problem.
You guys are awesome!
Thanks,
Alex
On May 12, 2010, at 10:12 PM, Alex Wang wrote:
Sorr
Sorry please discard my query results here, because I was playing with the
field type and changed it to "text" from "string" and forgot to change it back.
I will change it back to "string" and post the query results shortly.
I apologize for the careless mistake.
Thanks,
Alex
On May 12, 2010,
Thanks Hoss. Please see the query results as follows:
>
> :
> :
> :
> : productType:ProductBean
> :
> :
>
> ...can you please disable the QueryElevationComponent and see if that
> changes things?
>
> : productType:ProductBean
>
> What are the numFound values for these queries? (bot
Click the "schema browser" link on the admin page.
On the next page click
the "fields" link, then the field in question.
But first I'd do whatever Chris suggested.
BTW, the field definition you pasted isn't the one that
really counts here, "fieldtype" is the one that does, but in this case
th
:
:
:
: productType:ProductBean
:
:
...can you please disable the QueryElevationComponent and see if that
changes things?
: productType:ProductBean
What are the numFound values for these queries? (both with and w/o
QueryElevationComponent) ...
/admin/select?q=productType:[*+T
Erick,
I tried the lower case search (productType:productbean) and I did not get any
results either. Luke shows that "ProductBean" for the field, not sure whether
it's indexed term or stored term. Does this mean that this is not a case issue?
Here is the field definition in the schema:
Thank
Not til this evening, don't have a handy SOLR implementation to ping...
But another option is to get a copy of Luke and look at the index, but the
same caution
about seeing terms not stored data holds.
Or you could just try your troublesome search with all lower case for your
term (not field)
and
Sorry Erick, can you tell me how to find the raw *indexed* terms from the admin
console? I am not familiar with the admin console.
Thanks,
On May 12, 2010, at 10:18 AM, Erick Erickson wrote:
> Hmmm, nothing looks odd about that, except perhaps the casing. If you use
> the admin
> console to loo
Hmmm, nothing looks odd about that, except perhaps the casing. If you use
the admin
console to look at the raw terms, is productbean mixed case or all lower
case? If the
latter, that would explain things
Be a bit cautious because if you look at the *stored* data it will be in
mixed case, but
t
Sorry the previous copy & paste of the output seems to be messed up. Hope this
one is better:
0
15
true
on
0
productType:ProductBean
10
2.2
productType:ProductBean
productType:ProductBean
productType:ProductBean
productType:ProductBean
productType:ProductBean
Thanks Erick for your response. Here is the debugQuery output:
-<%5Cl%20%22%22>
-<%5Cl%20%22%22>
0
15
-<%5Cl%20%22%22>
true
on
0
productType:ProductBean
10
2.2
-<%5Cl%20%22%22>
-<%5Cl%20%22%22>
productType:ProductBean
productType:ProductBean
productType:ProductBean
What is the debug output of the query? That would shed some light on the
issue...
Best
Erick
On Tue, May 11, 2010 at 5:48 PM, Alex Wang wrote:
>
> Hi,
>
> I am getting a weird behavior in my Solr (1.4) index:
>
> I have a field defined as follows:
>
>
>
> and in all my index documents, the val
Hi,
I am getting a weird behavior in my Solr (1.4) index:
I have a field defined as follows:
and in all my index documents, the value of this field is "ProductBean"
(without quotes).
However, in the Solr admin console, when I type in the following query, I am
expecting all my documents to
14 matches
Mail list logo
