Thanks for sharing the post, finally I had the time to read it :)
It is really illuminating
On Fri, Jul 3, 2020 at 1:28 PM Toke Eskildsen wrote:
> On Fri, 2020-07-03 at 10:00 +0200, Vincenzo D'Amore wrote:
> > Hi Erick, not sure I got.
> > Does this mean that the order of values within a
Op vr 3 jul. 2020 om 14:11 schreef Bram Van Dam :
> On 03/07/2020 09:50, Thomas Corthals wrote:
> > I think this should go in the ref guide. If your product depends on this
> > behaviour, you want reassurance that it isn't going to change in the next
> > release. Not everyone will go looking
On 03/07/2020 09:50, Thomas Corthals wrote:
> I think this should go in the ref guide. If your product depends on this
> behaviour, you want reassurance that it isn't going to change in the next
> release. Not everyone will go looking through the javadoc to see if this is
> implied.
This is in
On Fri, 2020-07-03 at 10:00 +0200, Vincenzo D'Amore wrote:
> Hi Erick, not sure I got.
> Does this mean that the order of values within a multivalued field:
> - docValues=true the result will be both re-ordered and deduplicated.
> - docValues=false the result order is guaranteed to be maintained
Hi Erick, not sure I got.
Does this mean that the order of values within a multivalued field:
- docValues=true the result will be both re-ordered and deduplicated.
- docValues=false the result order is guaranteed to be maintained for
values in the insertion-order.
Is this correct?
On Thu, Jul 2,
I think this should go in the ref guide. If your product depends on this
behaviour, you want reassurance that it isn't going to change in the next
release. Not everyone will go looking through the javadoc to see if this is
implied.
Typically it'll either be something like "are always returned in
This is true _unless_ you fetch from docValues. docValues are SORTED_SETs,
so the results will be both ordered and deduplicated if you return them
as part of the field list.
Don’t really think it needs to go into the ref guide, it’s just inherent in
storing
any kind of value. You wouldn’t expect
Thanks, and genuinely asking: is there written somewhere in the
documentation too? If no, could anyone suggest to me which doc page should
I try to update?
On Thu, Jul 2, 2020 at 8:08 PM Colvin Cowie
wrote:
> The order of values within a multivalued field should match the insertion
> order. --
The order of values within a multivalued field should match the insertion
order. -- we certainly rely on that in our product.
Order is guaranteed to be maintained for values in a multi-valued field.
>
Hi all,
simple question: Solr float/double multivalue fields preserve the order of
inserted values?
Best regards,
Vincenzo
--
Vincenzo D'Amore
10 matches
Mail list logo
