On 13.08.2011 21:28 Erick Erickson wrote:
> Fair enough, but what's "first value in the list"?
> There's nothing special about "mutliValued" fields,
> that is where the schema has "multiValued=true".
> under the covers, this is no different than just
> concatenating all the values together and put
Fair enough, but what's "first value in the list"?
There's nothing special about "mutliValued" fields,
that is where the schema has "multiValued=true".
under the covers, this is no different than just
concatenating all the values together and putting them
in at one go, except for some games with th
On 13.08.2011 20:31 Martijn v Groningen wrote:
> The first solution would make sense to me. Some kind of a strategy
> mechanism
> for this would allow anyone to define their own rules. Duplicating results
> would be confusing to me.
That is why I would only activate it on request (setting a speci
I have a different use case. Consider a spatial multivalued field with latlong
values for addresses. I would want sort by geodist() to return the closest
distance in each group. For example find me the closest restaurant which each
doc being a chain name like pizza hut. Or doctors with multiple
The first solution would make sense to me. Some kind of a strategy
mechanism
for this would allow anyone to define their own rules. Duplicating results
would be confusing to me.
On 13 August 2011 18:39, Michael Lackhoff wrote:
> On 13.08.2011 18:03 Erick Erickson wrote:
>
> > The problem I've al
On 13.08.2011 18:03 Erick Erickson wrote:
> The problem I've always had is that I don't quite know what
> "sorting on multivalued fields" means. If your field had tokens
> a and z, would sorting on that field put the doc
> at the beginning or end of the list? Sure, you can define
> rules (
The problem I've always had is that I don't quite know what
"sorting on multivalued fields" means. If your field had tokens
a and z, would sorting on that field put the doc
at the beginning or end of the list? Sure, you can define
rules (first token, last token, average of all tokens (whate
Hi Johnny,
Sorting on a multivalued field has never really worked in Solr.
Solr versions <= 1.4.1 allowed it, but there was a change that an error
occurred and that the sorting might not be what you expect.
>From Solr 3.1 and up sorting on a multivalued isn't allowed and a http 400
is returned.
D
Hi,
There is no direct solution, you have to create single value field(s)
to create search. I am aware of two workarounds:
- you can use a random or a given (e.g. the first) instance of the
multiple values of the field, and that would be your sortable field.
- you can create two sortable fields:
Hi,
I am currently using SOLR 1.4.1, With this version sorting working fine even
in multivalued field.
Now I am planning to upgrade my SOLR version from 1.4.1 --> 3.3.0, In this
latest version sorting is not working on multivauled field.
So I am in unable to upgrade my SOLR due to this drawback.
10 matches
Mail list logo
