I find myself wishing we hadn't removed the unnecessary "throws MalformedURLException" from SolrJ client objects, because it would be a good way to detect inclusion of the "#" character in the URL -- which normally only happens when a user takes the URL from an admin UI session in their browser and uses it for SolrJ. From what I've seen in the past, the exception you get from doing this is completely unhelpful in tracking down the problem. I'll be trying it later today to remind myself exactly what a user sees.
If I build a patch that does this detection, should it throw a RuntimeException (maybe a descendant), or should I put MalformedURLException back in? Should CloudSolrServer attempt to handle this if it happens on an internal client object, or simply propagate the exception upwards? Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
