The /export handler uses DocValues to output the field list. It's a pretty big improvement in performance over stored fields. It supports single and multivalue numerics and strings so you can test out the various performance characteristics. Also as David mentioned DocValues has some nice options for trading off memory for performance.
Joel Bernstein Search Engineer at Heliosearch On Mon, Mar 2, 2015 at 3:26 PM, Chris Hostetter <[email protected]> wrote: > > : Hmm, this is indeed not documented. I'll fix. > > It's definitely documented... > > > https://cwiki.apache.org/confluence/display/solr/Transforming+Result+Documents > > https://cwiki.apache.org/confluence/display/solr/Function+Queries#FunctionQueries-UsingFunctionQuery > > https://cwiki.apache.org/confluence/display/solr/Function+Queries#FunctionQueries-AvailableFunctions > > ...the problem is it's specifically tied to the use of function queries, > and won't work very nicely for non-numerics of multivalued fields. > > What would be nice is to have an explicit [field] transformer like what i > proposed here, that included a localparam option to use DocValues instead > of Stored Fields... > > > https://issues.apache.org/jira/browse/SOLR-7070?focusedCommentId=14305965&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14305965 > > > -Hoss > http://www.lucidworks.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
