And the solr-ruby library handles this in the standard/dismax
responses in this manner:
def field_facets(field)
facets = []
values = @data['facet_counts']['facet_fields'][field]
Solr::Util.paired_array_each(values) do |key, value|
facets << FacetValue.new(key, value)
end
On Mon, Mar 10, 2008 at 4:42 PM, Matt M. <[EMAIL PROTECTED]> wrote:
> The sort order doesn't seem to work correctly when using the "map" (hash)
> type.
That's why it's not the default... I didn't want to put the burden of
re-sorting on the client.
-Yonik
I (and Erik) solved my problem! It was from a setting in the
solrconfig.xmlfile. Under the settings for the standard request. I
ended up copying the
schema from the acts_as_solr library, and didn't notice this one little
change:
map
That tells Solr to return the json result (or Ruby or Python) in
Just wanted to mention... the solr-ruby package has nothing to do with this.
These are responses straight out of the solr/select handler.
Matt
On Mon, Mar 10, 2008 at 12:07 PM, Matt M. <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've just noticed while switching connections between two different solr
>
Hi,
I've just noticed while switching connections between two different solr
instances (different servers) that their facet response structures are not
the same. But the Solr version is identical; 1.2. I've pasted in the
significant part of the response. Note the facet_fields in the first is a
Has
