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
the fieldtype is string, which stores things unanalyzed
so I'm probably waaaay off track with the capitalization question.

The analysis tool isn't looking in your index, it's
showing you what *would* happen to the text you type in
given the analyzers defined for the field you identify.
You can put totally bogus text in here and you'll still
get output...

So here's my guess. You're not indexing just the value
ProductBean, you're indexing "ProductBean blah blah blah".
Since you're using the string type, that's exactly what's
being indexed *as a single token*. Which is why
the wildcard stuff is working and ProductBean by itself
is not.

Try a "text" type rather than "string" and you might get some
joy. You'll have to restart Solr and reindex to see this....

Of course I may be off base *again* <G>.

Best
Erick

On Wed, May 12, 2010 at 11:27 AM, Alex Wang <aw...@crossview.com> wrote:

> 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 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
> > that's irrelevant to the search, you need to look at the *indexed* terms.
> >
> > HTH
> > Erick
>
>

Reply via email to