On 5/3/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
On 5/3/07, Jack L <[EMAIL PROTECTED]> wrote:
> The Python output uses nested dictionaries for facet counts.
This might be fixed in the future
It's fixed in the current development version (future 1.2), already.
See http://wiki.apache.org/solr/So
On 5/4/07, Jack L <[EMAIL PROTECTED]> wrote:
I use this to sort the facet field values against count in
reverse order in Python:
sorted(facet_field_values.items(), lambda x, y: cmp(x[1], y[1]), reverse = True)
FWIW, the key= parameter is generally more efficient for python 2.4+:
sorted(facet.
I use this to sort the facet field values against count in
reverse order in Python:
sorted(facet_field_values.items(), lambda x, y: cmp(x[1], y[1]), reverse = True)
Thursday, May 3, 2007, 6:18:05 PM, you wrote:
> We resort it in solr-ruby:
>def field_facets(field)
> facets = []
>
We resort it in solr-ruby:
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
facets
end
On May 3, 2007, at 8:10 PM, Mike Klaas wr
On 5/3/07, Jack L <[EMAIL PROTECTED]> wrote:
The Python output uses nested dictionaries for facet counts.
I read it online that Python dictionaries do not preserve order.
So when a string is eval()'d, the sorted order is lost in the
generated Python object. Is it a good idea to use list to wrap
a
The Python output uses nested dictionaries for facet counts.
I read it online that Python dictionaries do not preserve order.
So when a string is eval()'d, the sorted order is lost in the
generated Python object. Is it a good idea to use list to wrap
around the dictionary? This is only needed for t
When facet.sort is used, the facet fields are sorted by the count
in the reply string when using python output. However, after calling
eval(), the sort order seems to be lost. Not sure if anyone has come
up with a way to avoid this problem.
Using the JSON output with a JSON parser for Python shou
