On Feb 1, 2010, at 8:45 PM, Matthieu Labour wrote:
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?
Yes, that's a trick in Solr to ignore a field. The e
Erik Hatcher wrote:
From: Erik Hatcher
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&
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 t
Both index="analyzed" and store="yes" are not parsed by Solr schema.
Use indexed and stored instead of index and store, and set either "true"
or "false".
Koji
--
http://www.rondhuit.com/en/
Hi
on the following field
[...]
[...]
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.
[...]
[...]
I ha
