Moreover, you may be trying to save/optimize in a wrong place. Maybe these additional indexed fields are not so costly. Maybe you can optimize in some other part of your setup.
Otis Solr & ElasticSearch Support http://sematext.com/ On Sep 18, 2013 5:47 PM, "Chris Hostetter" <hossman_luc...@fucit.org> wrote: > > : Subject: Re: Querying a non-indexed field? > : > : No. --wunder > > To elaborate just a bit... > > : query on a few indexed fields, getting a small # of results. I want to > : restrict this further based on values from non-indexed, stored fields. > : I can obviously do this myself, but it would be nice if Solr could do > > ...you could implement this in a custom SearchComponent, or custom qparser > that would generate PostFilter compatible queries, that looked at the > stored field values -- but it's extremeley unlikeley that you would ever > convince any of the lucene/solr devs to agree to commit a general purpose > version of this type of logic into the code base -- because in the general > case (arbitrary unknown number of documents matching the main query) it > would be extremely inefficient and would encourage "bad" user behavior. > > -Hoss >
