[SOLR-8030] Transaction log does not store the update chain (or req params?) used for updates

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.3
• Component/s: SolrCloud
• Assignee: Unassigned
• Reporter: Ludovic Boutros
• Created: 10/Sep/15 13:17
• Updated: 30/Mar/20 20:13

Description

Transaction Log does not store the update chain, or any other details from the original update request such as the request params, used during updates.

Therefore tLog uses the default update chain, and a synthetic request, during log replay.

If we implement custom update logic with multiple distinct update chains that use custom processors after DistributedUpdateProcessor, or if the default chain uses processors whose behavior depends on other request params, then log replay may be incorrect.

Potentially problematic scenerios (need test cases):

• DBQ where the main query string uses local param variables that refer to other request params
• custom Update chain set as default="true" using something like StatelessScriptUpdateProcessorFactory after DUP where the script depends on request params.
• multiple named update chains with diff processors configured after DUP and specific requests sent to diff chains – ex: ParseDateProcessor w/ custom formats configured after DUP in some special chains, but not in the default chain

Issue Links

• relates to: SOLR-9883 example solr config files can lead to invalid tlog replays when using add-unknown-fields-to-schema updat chain