Re: indexed and stored for fields that are sources of a copy field

>>> >>> I have a number of fields defined in my managed-schema file that are used >>> as the sources for a copy field: >>> >>> >> stored="true"/> >>> >> stored="true" multiValued="true"/>

Re: indexed and stored for fields that are sources of a copy field

lting Support Training - http://sematext.com/ On 22 Oct 2018, at 15:22, Chris Wareham wrote: Hi folks, I have a number of fields defined in my managed-schema file that are used as the sources for a copy field: Can I set both the indexed and stored values to false for the

Re: indexed and stored for fields that are sources of a copy field

alued="true"/> > > stored="false" multiValued="true"/> > > > > > > Can I set both the indexed and stored values to false for the body, sectors > and locations fields since I don't want to search or retrieve them? > > Regards, > > Chris

indexed and stored for fields that are sources of a copy field

Hi folks, I have a number of fields defined in my managed-schema file that are used as the sources for a copy field: stored="true"/> stored="true" multiValued="true"/> stored="true" multiValued="true"/> stored="false&

Re: indexed and stored fields don't appear in the response

You're confusing indexing and storing. You can _search_ on anything where indexed="true", thus your q=bizid: 2380505101 query returns documents (I'm assuming) works. That has nothing to do with what's returned in your documents. For seeing a field in your documents for which you've set stored="tr

Re: indexed and stored fields don't appear in the response

Thanks for Anshum & Gora's suggestion. I haven't set default fl in solrconfig.xml and the documents do contain tagid and bizid field(I've tried both q=*:* and q=bizid:2380505101). I'll look into the reindex possibility that Gora mentioned. 2015-02-09 18:37 GMT+08:00 Gora Mohanty : > On 9 February

Re: indexed and stored fields don't appear in the response

On 9 February 2015 at 15:50, Anshum Gupta wrote: > Common reasons for that would be > 1. Your default fl in solrconfig is set to id, _version_. Can you try > explicitly mentioning fl=id,tagid,bizid in the request? Also, it'd be good > to look at your solrconfig.xml. > 2. Chances are, those documen

Re: indexed and stored fields don't appear in the response

Common reasons for that would be 1. Your default fl in solrconfig is set to id, _version_. Can you try explicitly mentioning fl=id,tagid,bizid in the request? Also, it'd be good to look at your solrconfig.xml. 2. Chances are, those documents do not contain those fields to begin with. Both bizid and

Re: indexed and stored fields don't appear in the response

Sorry about the error, I have copied the wrong schema file :( The schema.xml file is actually as follows: The command curl "http://localhost:8983/solr/pa_info/select? q=bizid:2380505101&rows=10 " will get the following response:

Re: indexed and stored fields don't appear in the response

What happens? You seem to be getting back the stored fields for the top 10 documents. What do you want/think should happen? On Mon, Feb 9, 2015 at 12:56 AM, Sandy Ding wrote: > Part of my schema is as follows: > > > required="true" multiValued="false" docValues="true" /> > requir

Re: indexed and stored fields don't appear in the response

> > When I issue the following command, > > curl "http://localhost:8983/solr/pa_info/select?q=*:*&rows=10"; > > The response is: > > > 0 name="QTime">16*:* name="rows">10 start="0" maxScore="1.0">659404

indexed and stored fields don't appear in the response

Part of my schema is as follows: When I issue the following command, curl "http://localhost:8983/solr/pa_info/select?q=*:*&rows=10"; The response is: 016*:*106594047971492348841962242048101233589714923488419632906261783978259149234884196329062711972893031492348841963290629

Re: Different values for the indexed and stored data

Hi Jayesh, Solr already works like that. Returned fields (fl) will have original data. On Thursday, May 22, 2014 8:02 PM, Jayesh Sidhwani wrote: Hello folks, I use SOLR to store e-commerce product data. I wanted to understand if there's any way in which we can store the index data different

Different values for the indexed and stored data

Hello folks, I use SOLR to store e-commerce product data. I wanted to understand if there's any way in which we can store the index data differently from the data that I expect solr to send as a result? For example; consider that a category is called T-Shirt. When I query solr, I want to be able

Re: Indexed And Stored

now i have two different files. so if i try to update previous file for indexed = true. it erase new field -- View this message in context: http://lucene.472066.n3.nabble.com/Indexed-And-Stored-tp4039893p4039930.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Indexed And Stored

gt; and i updated 18 data. > now i need indexed="true" for all old data. > i need solution > please someone help me out. > please reply urgent!! > thanks > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Indexed-And-Stored-tp40

Re: Indexed And Stored

On 12 February 2013 15:49, anurag.jain wrote: > hello, > > in my schema > > > > and i updated 18 data. > > > now i need indexed="true" for all old data. > > i need solution [...] You have no choice but to change the schema, and reindex, either from the original source, or by first pulling fr

Indexed And Stored

hello, in my schema and i updated 18 data. now i need indexed="true" for all old data. i need solution please someone help me out. please reply urgent!! thanks -- View this message in context: http://lucene.472066.n3.nabble.com/Indexed-And-Stored-tp4039893.html

Re: schema.xml: default values for @indexed and @stored

Otis Gospodnetic schrieb: Attribute values for fields should be inherited from attribute values of their field types. Thanks, that answers my question pertaining to @indexed and @stored in the "fieldtype" and "field" elements in "schema.xml". Michael Ludwig

Re: schema.xml: default values for @indexed and @stored

:08:43 PM > Subject: schema.xml: default values for @indexed and @stored > > From the apache-solr-1.3.0\example\solr\conf\schema.xml file: > > > > class="solr.StrField" /> > > So for both fieldtype/@stored and fieldtype/@indexed, the default is > "tru

schema.xml: default values for @indexed and @stored

From the apache-solr-1.3.0\example\solr\conf\schema.xml file: So for both fieldtype/@stored and fieldtype/@indexed, the default is "true", correct? And does the configuration constitute a default for so that field/@stored and field/@indexed take their effective values according to field/@ty