[SOLR-12535] Remove syntax for providing index boosts in Solr's JSON update syntax

• Type: Task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 8.0
• Assignee: David Smiley
• Reporter: David Smiley
• Created: 03/Jul/18 21:28
• Updated: 08/Jun/19 15:01
• Resolved: 26/Dec/18 14:40

Description

In Solr 7 we can't index boost as it's gone from Lucene. The JSON support for this syntax is still allowed but logs a warning and doesn't apply the boost (as it's not supported). I'm proposing we remove support for this altogether. This also means removing an little-known way to specify an "extended field value" that doesn't necessarily have a boost.
With boost: Today logs a warning. Don't want this to work at all.

[{'id':'1', 'val_s':{'value':'foo', 'boost':2.0}}]

Without boost: Today works. Don't want this to work at all, as it complicates support for labelled child documents – SOLR-12362.

[{'id':'1', 'val_s':{'value':'foo'}}]

Internally this is parsed by
org.apache.solr.handler.loader.JsonLoader.SingleThreadedJsonLoader#parseExtendedFieldValue
I think we need make no reference to the notion of an "extended field value". Either we have a "partial update", or we have a "child document"; nothing else.

https://lucene.apache.org/solr/guide/7_3/updating-parts-of-documents.html

Note: partial updates look similar and have exactly one field-value using a limited set of verbs like "set":

[{'id':'1', 'val_s':{'set':'foo'}}]