David Smiley created SOLR-12535:
-----------------------------------
Summary: Remove syntax for providing index boosts in Solr's JSON
update syntax
Key: SOLR-12535
URL: https://issues.apache.org/jira/browse/SOLR-12535
Project: Solr
Issue Type: Task
Security Level: Public (Default Security Level. Issues are Public)
Reporter: David Smiley
Fix For: master (8.0)
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.*
{code:java}
[{'id':'1', 'val_s':{'value':'foo', 'boost':2.0}}]
{code}
Without boost: Today works. *Don't want this to work at all,* as it complicates
support for labelled child documents – SOLR-12441.
{code:java}
[{'id':'1', 'val_s':{'value':'foo'}}]
{code}
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":
{code}
[{'id':'1', 'val_s':{'set':'foo'}}]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
