: We took a deeper look at what happened, when an "external-file-field"-Request
is sent to SOLR:
:
: * SOLR looks if there is a file for the requested query, e.g. "trousers"
Something smells fishy here.
ExternalFileField is designed to let you load values for a field (for use
in functions) from a file where the file name is determined from the field
name
If ExternalFileField is trying to load a file named "external_trousers"
that means your query is attempting ot use "trousers" as a *field* ...
that doesn't sound right.
based on your description of the memory blow up you are seeing, it sounds
like you are using the user's query string as a (dynamic?) field name and
none of these external_${query} files exist -- that's not really the
intended usage.
Can you clarify a bit more what exactly your goal is? This smells like an
XY Problem (my gut reaction is that you might actaully be wanting to
use QueryElevationComponent instead of ExternalFileField)...
http://people.apache.org/~hossman/#xyproblem
XY Problem
Your question appears to be an "XY Problem" ... that is: you are dealing
with "X", you are assuming "Y" will help you, and you are asking about "Y"
without giving more details about the "X" so that we can understand the
full issue. Perhaps the best solution doesn't involve "Y" at all?
See Also: http://www.perlmonks.org/index.pl?node_id=542341
-Hoss
