Koji, Eric
Thank you for your reply
One more question:
What about a field that is both indexed="false" stored="false" ... does it have
an impact into solr meaning is it being ignored by solr/lucene? is it like the
field was not being passed?
Thank you!
--- On Mon, 2/1/10, Erik Hatcher <erik.hatc...@gmail.com> wrote:
From: Erik Hatcher <erik.hatc...@gmail.com>
Subject: Re: query on not stored field
To: solr-user@lucene.apache.org
Date: Monday, February 1, 2010, 6:32 PM
First of all, the schema snippets you provided aren't right. It's
indexed="true", not index="analyzed". And it's stored, not store.
But, to answer your question, the stored nature of the field has nothing
whatsoever to do with it's searchability. Stored only affects whether you can
get that value back in the documents returned from a search, or not.
Erik
On Feb 1, 2010, at 7:12 PM, Matthieu Labour wrote:
> Hi
>
> on the following field
>
> <fields name="status">
> [...]
> <field name="message" index="analyzed" store="yes" default="true"/>
> [...]
> </fields>
>
> the following query works
>
> {!lucene q.op=AND} [...] AND (status.message&STRING_ANALYZED_NO_US:(some
> keywords) AND [...]
>
> I was wondering If the query syntax above works as well if the store property
> of the field is set to NO.
>
> <fields name="status">
>
> [...]
>
> <field name="message" index="analyzed" store="no" default="true"/>
>
> [...]
>
> </fields>
>
>
> I have tried it and it seems to work. I would appreciate if someone could
> confirm!
>
> Thank you
>
>
>
>
>
