[ https://issues.apache.org/jira/browse/SOLR-16810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724762#comment-17724762 ]
Gus Heck commented on SOLR-16810: --------------------------------- Wait, if this is only an xml thing, then the # symbol shouldn't have been escaped to begin with... what are we using to escape xml attributes? '#' is perfectly legal in an xml attribute. The only thing that needs escaped is & < and whichever delimiter is used (' or "). '#' is only significant if preceded by & and followed by numbers (character reference), but once the & gets escaped that's not an issue anymore and nothing else needs to be escaped. [https://www.w3.org/TR/xml/#NT-AttValue] > Under certain situations Solr produces managed schema XML that cannot be > loaded > ------------------------------------------------------------------------------- > > Key: SOLR-16810 > URL: https://issues.apache.org/jira/browse/SOLR-16810 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Schema and Analysis > Affects Versions: 9.2.1 > Reporter: Thiruvalluvan M. G. > Assignee: Ishan Chattopadhyaya > Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > While persisting the {{ManagedIndexSchema}} as XML, non-printable characters > in field names get escaped as {{{}#nn;{}}}, where {{nn}} is the decimal > representation of the non-printable character. For example, if the field name > has the byte {{{}0x14{}}}, it gets escaped as {{{}#20;{}}}. This in > indistinguishable from the literal {{#20;}} in the field name. If we have two > fields - one with the non-printable character and the other with the literal > string, two fields get generated with the same name. Loading the resulting > XML, naturally, causes an exception. To fix this, any occurrence of literal > {{#}} in the field name should be escaped, with say {{{}##{}}}. > A second problem is that while escaping happens when generating XML, the > corresponding unescaping does not happen on loading it. This asymmetry should > be fixed as well. -- 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