[
https://issues.apache.org/jira/browse/SOLR-16155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626371#comment-17626371
]
David Smiley commented on SOLR-16155:
-------------------------------------
This is debatable. In "production" – okay. When in "dev", it's helpful
information! Imagine loading a CSV file and not knowing which value it was
that had some weird syntax that caused a date to parse wrong (for example).
Maybe it was an extra quotation mark or who knows what. At least the
document's ID is generally printed so we can figure things out. I'm not
standing in the way of this change if others want it, but understand we're
losing usability for newcomers if we do this.
> DocumentBuilder should not include field values in error messages
> -----------------------------------------------------------------
>
> Key: SOLR-16155
> URL: https://issues.apache.org/jira/browse/SOLR-16155
> Project: Solr
> Issue Type: Bug
> Components: logging
> Affects Versions: 8.11.1
> Reporter: Jerry Chung
> Priority: Critical
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> org.apache.solr.update.DocumentBuilder throws exceptions with field values on
> errors, which could reveal customer's sensitive data on log files and UI.
> Field values shouldn't be included in the error messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
