[
https://issues.apache.org/jira/browse/SOLR-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567143#comment-13567143
]
Karl Wright commented on SOLR-4390:
-----------------------------------
I guess there are two issues here.
ManifoldCF often "discovers" metadata names in some repositories (this one is
LiveLink), whose names don't obey the Solr "legality" constraint you mention.
If you want to reject or ignore these at the Solr level, well okay, but
definitely a SolrJ runtime exception seems like a heavy-handed way of doing
that.
The second issue is that there are existing clients of ManifoldCF that were
able to index this content before we went to SolrJ. I don't know how they do
it but they were happy with it before.
> 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]
