I've added a case with patch here: https://issues.apache.org/jira/browse/SOLR-2731
On Wed, Aug 24, 2011 at 11:59 AM, Jon Hoffman <j...@foursquare.com> wrote: > I took a look at the source and agree that it would be a bit hairy to > bubble up header settings from the response writers. > > Alternatively, and I'll admit that this is a somewhat hacky proposal, an > optional parameter "csv.numfound=true" could be added to the request which > would cause the first line of the response to be the numfound. It would > have no impact on existing behavior, and those who are interested in that > value can simply read off the first line before sending to their usual csv > parser. > > It's a trivial change to the code and I can create a JIRA ticket and submit > the patch. > > This is my first interaction with this forum, so let me know if the dev > list is a more appropriate place to propose changes. > > - Jon > > > On Wed, Aug 24, 2011 at 10:47 AM, Erik Hatcher <erik.hatc...@gmail.com>wrote: > >> Good idea. However response writers can't control HTTP response headers >> currently... Only the content type returned. >> >> Erik >> >> On Aug 24, 2011, at 8:52, Jon Hoffman <j...@foursquare.com> wrote: >> >> > What about the HTTP response header? >> > >> > >> >>> Great question. But how would that get returned in the response? >> >>> >> >>> It is a drag that the header is lost when results are written in CSV, >> but >> >> there really isn't an obvious spot for that information to be returned. >> >> >> >> I guess a comment would be one option. >> >> >> >> -Yonik >> >> http://www.lucidimagination.com >> >> >> >> >> >> >> > >
