[
https://issues.apache.org/jira/browse/SOLR-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567131#comment-13567131
]
Erik Hatcher commented on SOLR-4390:
------------------------------------
But do keep in mind that "legal" (happiest path for all pieces of Solr) field
names are basically comprised of only [A-Za-z0-9_], which is the use case you
mention using literal.<funky field name>=... parameters.
> SolrJ does not URL-encode query string argument names but should
> ----------------------------------------------------------------
>
> Key: SOLR-4390
> URL: https://issues.apache.org/jira/browse/SOLR-4390
> Project: Solr
> Issue Type: Bug
> Components: clients - java
> Affects Versions: 4.1
> Reporter: Karl Wright
>
> SolrJ does not appear to URL-encode any metadata names, but should. This
> leads to URLs that are illegal, and thus an IllegalArgumentException gets
> thrown. See CONNECTORS-630 for an example of a bad URL that SolrJ generates.
> I understand that this may have been broken for a long time and that now
> backwards-compatibility is an issue, but it should still be possible to tell
> SolrJ to do the right thing and not make the SolrJ user do it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
