Dan, If you don't mind using a float format DocValues field, you could
store NAN (Not A Number). But any sorting operations would be slower, or
size comparisons. Floats might be entirely inappropriate, but I thought
it is worth a mention. Cheers -- Rick
On 2017-05-04 10:55 AM, Dan . wrote:
H
Hi Dan,
In-place updates are working because index size does not change. Atomic
(or any other updates) are flagging existing doc as deleted and writing
it again, so even if it removes some fields, such updates are making
index larger until segment with deleted doc is merged.
In-place updates
Hi Emir,
Yes I though of representing -1 as null, but this makes the index
unnecessarily larger, particularly if we have to default all docs to this
value.
Cheers,
Dan
On 4 May 2017 at 15:16, Emir Arnautovic
wrote:
> Hi Dan,
>
> Remove does not make sense when it comes to in-place updates of
Hi Shawn,
Thanks for the suggestion.
I gave that a try but unfortunately it didn't work.
Delete somehow would be really useful, seems wasteful to have e.g. -1
representing null.
Cheers,
Dan
On 4 May 2017 at 15:30, Shawn Heisey wrote:
> On 5/4/2017 7:40 AM, Dan . wrote:
> > I have a field lik
On 5/4/2017 7:40 AM, Dan . wrote:
> I have a field like this:
>
>
> docValues="true" multiValued="false"/>
>
> so I can do a fast in-place atomic updates
>
> However if I do e.g.
>
> curl -H 'Content-Type: application/json'
> 'http://localhost:8983/solr/collection/update?commit=true'
> --data-bin
Hi Dan,
Remove does not make sense when it comes to in-place updates of
docValues - it has to have some value, so only thing that you can do is
introduce some int value as null.
HTH,
Emir
On 04.05.2017 15:40, Dan . wrote:
Hi,
I have a field like this:
so I can do a fast in-place atomi
Hi,
I have a field like this:
so I can do a fast in-place atomic updates
However if I do e.g.
curl -H 'Content-Type: application/json'
'http://localhost:8983/solr/collection/update?commit=true'
--data-binary '
[{
"id":"my_id",
"popularity":{"set":null}
}]'
then I'd expect the popularity f
