Jason Gerlowski created SOLR-14443:
--------------------------------------
Summary: Make SolrLogPostTool resilient to unexpected requests
Key: SOLR-14443
URL: https://issues.apache.org/jira/browse/SOLR-14443
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: scripts and tools
Affects Versions: master (9.0)
Reporter: Jason Gerlowski
Assignee: Jason Gerlowski
When SolrLogPostTool parses log messages corresponding to incoming requests, it
sets various predefined fields based on the parameters on the request. e.g. it
sets a rows_i field, a wt_s field, and so on.
This logic works for most requests, but if the log-parser encounters requests
with multiple of these params (e.g. rows), it will blithely add them to the
SolrInputDocument, and error out when Solr rejects the eventual update request
because it is attempting to put multiple values into a single-valued field.
We can do two things to fix this.
# Make SolrLogPostTool's "posting" code resilient to individual update
failures. It doesn't make any sense to crash the entire posting routine just
because one batch (or one log message) was malformed.
# Tweak the field parsing logic to be more resilient to the specific
"redundant query params" case I encountered specifically here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
