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 <emir.arnauto...@sematext.com> wrote: > 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: >> >> <fieldType name="integer" class="solr.TrieIntField" omitNorms="true"/> >> <field name="popularity" type="integer" indexed="false" stored="false" >> 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-binary ' >> [{ >> "id":"my_id", >> "popularity":{"set":null} >> }]' >> >> then I'd expect the popularity field to be removed, however it's not. >> >> I this a bug? or is there a know workaround for this for in-place atomic >> updates? >> >> Cheers, >> Dan >> >> > -- > Monitoring * Alerting * Anomaly Detection * Centralized Log Management > Solr & Elasticsearch Support * http://sematext.com/ > >
