Yes as i said earlier
. If you want to store the value of field as it is in index without
Tokenizing . .for example customer_id which is a unique fields and you
don't want to tokenize
when you index a field you could tokenize the field values to index based on
what tokenizer you use so that us
Thanks for making me understand the concept of indexing and storing field.
now i got the point :)
-
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/problem-in-setting-field-attribute-in-schema-xml-tp2984126p2988516.html
Sent from the Solr - User mailing list archive a
:), Thanks.. now i got the purpose of indexed and store.
-
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/problem-in-setting-field-attribute-in-schema-xml-tp2984126p2988506.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi Romi,
as someone mentioned earlier already:
indexed - The field value can be "matched" when you search on that
field (field:"some-value-to-match")
stored -The field value can be "retrieved" from Solr in result sets
(result docs can include that field and its value)
@ Indexing i
Am 26.05.2011 14:10, schrieb Romi:
did u mean when i set indexed="false" and store="true", solr does not index
the field's value but store its value as it is???
I don't know if you are asking me since you do not quote anything but
yes of course this is exactly the purpose of "indexed" and "sto
On Thu, May 26, 2011 at 2:10 PM, Romi wrote:
> did u mean when i set indexed="false" and store="true", solr does not index
> the field's value but store its value as it is???
Yes. So you can get back the value of all stored fields even if your
search actually only finds results in indexed fields.
did u mean when i set indexed="false" and store="true", solr does not index
the field's value but store its value as it is???
-
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/problem-in-setting-field-attribute-in-schema-xml-tp2984126p2988458.html
Sent from the Solr -
Am 26.05.2011 12:52, schrieb Romi:
i have done it, i deleted old indexes and created new indexes but still able
to search it through *:*, and no result when i search it as field:value.
really surprising result. :-O
I really don't understand your problem. Thist is not at all surprising
but the
I guess you are indexing with property index=false , stored = true
if it is , that means you are storing the value on "index" , so whenever
you do *:* you can see the stored value
for example
if you have a field = ID, Customer_Name and you would only like to index
"customer_name" becaus
i have done it, i deleted old indexes and created new indexes but still able
to search it through *:*, and no result when i search it as field:value.
really surprising result. :-O
-
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/problem-in-setting-field-attribute-in
Well I'm probably being overly cautious here but its been my
experience that if I have a schema that says indexed = true on a field
and I change it to indexed = false I have to delete my index to get
rid of everything that was indexed with the old schema and I have to
restart to be able to index wi
i deleted my index but what do u mean by restart with new schema??
-
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/problem-in-setting-field-attribute-in-schema-xml-tp2984126p2988197.html
Sent from the Solr - User mailing list archive at Nabble.com.
>From my experience if it is indexing content that you have told it not
to index that is because you haven't cleared your old indexed content.
If you index something using schema version 5 which says indexed =
true and then you change it to indexed = false you have to delete your
old indexed conten
thanks a lot bryan: it might be again the repetition, but i just want to know
WHY it is indexing the field when it is indexed="false", what if
stored="true", it is clearly written in documentation that a field is search
able only if it is indexed="true", which surely make sense.
and my application
> ya...but when i set indexed="false" for a particular field, and i search as
> *:* then it will search all documents thats true, but what i think is it
> should not contain the field which i set as indexed="true".
> for example in a document fields are id, author,title. and i for author
> field i
even though i am running command for full-import, then also i deleted old
indexes , re created indexes, i am not using defaultSearchFiled and
copyingField attribute, still i am getting the search result for the field
which i set as indexed="true", really strange, please help me to get rid of
this p
"indexed" controls whether you can find the document based on the content of
this field.
"stored" controls whether you will see the content of this field in the
result.
ya...but when i set indexed="false" for a particular field, and i search as
*:* then it will search all documents thats true, bu
I tried deleting the index and trying it again. But still I get the same
result.
Regards
Vignesh
-Original Message-
From: Jan Høydahl [mailto:jan@cominvent.com]
Sent: 25 May 2011 19:30
To: solr-user@lucene.apache.org
Subject: Re: problem in setting field attribute in schema.xml
You
Am 25.05.2011 15:47, schrieb Vignesh Raj:
It's very strange. Even I tried the same now and am getting the same result.
I have set both indexed=false and stored=false.
But still if I search for a keyword using my default search, I get the
results in these fields as well.
But if I specify field:val
sh
>
>
> -Original Message-
> From: Romi [mailto:romijain3...@gmail.com]
> Sent: 25 May 2011 18:42
> To: solr-user@lucene.apache.org
> Subject: Re: problem in setting field attribute in schema.xml
>
> if i do stored=false then it indexes the data but not shows the data i
plain?
Regards
Vignesh
-Original Message-
From: Romi [mailto:romijain3...@gmail.com]
Sent: 25 May 2011 18:42
To: solr-user@lucene.apache.org
Subject: Re: problem in setting field attribute in schema.xml
if i do stored=false then it indexes the data but not shows the data in
search r
On 5/25/2011 9:29 AM, Romi wrote:
> and in http://wiki.apache.org/solr/SchemaXml#Fields it is clearly mentioned
> that a non-indexed field is not searchable then why i am getting search
> result. why should stored="true" matter if indexed="false"
"indexed" controls whether you can find the documen
If i do uniqueField to indexed="false" then it shows the exception
org.apache.solr.common.SolrException: Schema Parsing Failed
and in http://wiki.apache.org/solr/SchemaXml#Fields it is clearly mentioned
that a non-indexed field is not searchable then why i am getting search
result. why should sto
surely it indexes the data if you do indexed = true.
if you put some data in the field that is unique to that document and
then search do you get it? If not then it is because it is not
indexed. If you do a search for another field in the same document but
still get the non-indexed field shown it
if i do stored=false then it indexes the data but not shows the data in
search result. but in my case i do not want to index the data for a field
and to the my surprise even if i am doing indexed="false" for this field, i
am still able to get that data through the query *:* but not getting the
data
if you never want to see a result for a field set stored = false.
Best Regards,
Bryan Rasmussen
On Wed, May 25, 2011 at 2:37 PM, Romi wrote:
> In my schema.xml file i made a filed attribute indexed=false and stored=true.
> ie. i am not indexing this field but still in my search results i am gett
Please reply, i am not getting any of my problems reply in this forum.
-
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/problem-in-setting-field-attribute-in-schema-xml-tp2984126p2984151.html
Sent from the Solr - User mailing list archive at Nabble.com.
27 matches
Mail list logo
