If you enable LazyLoading and do not request them in your 'fl' list,
they should be mostly just size on disk AFAIK.
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 17 December 2015 at 08:09, Jamie Johnson wrote:
> The expense i
The expense is in gathering the pieces to do the indexing. There isn't
much that I can do in that regard unfortunately. I need to investigate
storing the fields, if they aren't returned is the expense just size on
disk or is there a memory cost as well?
On Dec 16, 2015 7:43 PM, "Alexandre Rafalov
ExternalFileField might be useful in some situations.
But also, is it possible that your Solr schema configuration is not
best suited for your domain? Is it - for example - possible that the
additional data should be in child records?
Pure guesswork here, not enough information. But, as described
What is the nature of your documents that reproducing them is so expensive?
Whatever it is, you should spend some time trying to reduce it to something
more manageable and performant. Generally, the primary recommendation is to
simply reindex any documents that need to be updated since atomic updat
The only way to do this currently is with Atomic Updates, which
require all fields to be stored except the destinations of copyField
directives. see:
https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents
Best,
Erick
On Wed, Dec 16, 2015 at 7:09 AM, Jamie Johnson wrote:
>
