I think the container is the issue (the type of rsp).
Here is the Javadoc for SimpleOrderedMap:
/** SimpleOrderedMap is a [EMAIL PROTECTED] NamedList} where access
by key is more
* important than maintaining order when it comes to representing the
* held data in other forms, as ResponseWriters n
Looks like it's only happening when we use the LocalSolrQueryComponent from
localsolr.
rsp.add("response", sdoclist);
sdoclist is a SolrDocumentList. Could that be causing an issue instead of it
being just a DocList?
Doug
Yonik Seeley wrote:
The output you showed is indeed incorrect, but I
The output you showed is indeed incorrect, but I can't reproduce that
with stock solr.
Here is a example of what I get:
{
'responseHeader'=>{
'status'=>0,
'QTime'=>16,
'params'=>{
'wt'=>'ruby',
'indent'=>'true',
'q'=>'*:*',
'facet'=>'true',
'highlight
Sure.
The default (json.nl=flat):
'response',{'numFound'=>41,'start'=>0,
Adding json.nl=map makes output correct:
'response'=>{'numFound'=>41,'start'=>0,
This also changes facet output (which was evaluating fine):
FLAT:
'facet_counts',{
'facet_queries'=>{},
'fac
On Wed, Mar 5, 2008 at 11:25 AM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
> If you don't add the json.nl=map to your params, then you can't eval() what
> you get back in Ruby
> ("can't convert String into Integer").
Can you show what the problematic ruby output is?
json.nl=map isn't the def
Note that we now have to add a default param to the requestHandler:
explicit
map
collapse
localsolr
facet
If you don't add the json.nl=map to your params, then you can't eval() what you get ba
Sweet. Thanks.
Doug
Yonik Seeley wrote:
Thanks Doug, I just checked in your fix.
This was a recent bug... writing of SolrDocument was recently added
and is not touched by normal code paths, except for distributed
search.
-Yonik
On Wed, Mar 5, 2008 at 9:29 AM, Doug Steigerwald
<[EMAIL PROTECT
Thanks Doug, I just checked in your fix.
This was a recent bug... writing of SolrDocument was recently added
and is not touched by normal code paths, except for distributed
search.
-Yonik
On Wed, Mar 5, 2008 at 9:29 AM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
> We're using localsolr and the R
We're using localsolr and the RubyResponseWriter. When we do a request with the localsolr component
in our requestHandler we're seeing issues with the display of a multivalued field when it only has
one value.
'class'=>['showtime']'showtime', <--
'genre'=>['Drama',
'Suspsense/Triller