g/viewvc/lucene/dev/tags/lucene_solr_4_6_1/solr/example/solr/collection1/conf/schema.xml?view=log
-- Jack Krupansky
-Original Message- From: Michael Sokolov
Sent: Saturday, March 15, 2014 1:02 PM
To: solr-user@lucene.apache.org
Subject: example schema now stores most field values
While upg
ucene_solr_4_6_1/solr/example/solr/collection1/conf/schema.xml?view=log
>>
>> -- Jack Krupansky
>>
>> -Original Message- From: Michael Sokolov
>> Sent: Saturday, March 15, 2014 1:02 PM
>> To: solr-user@lucene.apache.org
>> Subject: example schema now
upansky
-Original Message- From: Michael Sokolov
Sent: Saturday, March 15, 2014 1:02 PM
To: solr-user@lucene.apache.org
Subject: example schema now stores most field values
While upgrading from 4.2.1 to 4.6.1 I noticed that many of the fields
defined in the example schema.xml that used to
e/dev/tags/lucene_solr_4_6_1/solr/example/solr/collection1/conf/schema.xml?view=log
-- Jack Krupansky
-Original Message-
From: Michael Sokolov
Sent: Saturday, March 15, 2014 1:02 PM
To: solr-user@lucene.apache.org
Subject: example schema now stores most field values
While upgrading fro
Yes, that (https://wiki.apache.org/solr/Atomic_Updates) would make
sense; thanks for the insight.
-Mike
On 3/15/2014 1:07 PM, Yonik Seeley wrote:
Perhaps so atomic updates work?
-Yonik
http://heliosearch.org - solve Solr GC pauses with off-heap filters
and fieldcache
On Sat, Mar 15, 2014 at
Perhaps so atomic updates work?
-Yonik
http://heliosearch.org - solve Solr GC pauses with off-heap filters
and fieldcache
On Sat, Mar 15, 2014 at 1:02 PM, Michael Sokolov
wrote:
> While upgrading from 4.2.1 to 4.6.1 I noticed that many of the fields
> defined in the example schema.xml that used
While upgrading from 4.2.1 to 4.6.1 I noticed that many of the fields
defined in the example schema.xml that used to be indexed and not stored
are now defined as indexed and stored. Is there anything behind this
change other than the idea that it would be more convenient to have all
the values
