xtenzQ commented on PR #1829:
URL: https://github.com/apache/solr/pull/1829#issuecomment-1682258831
> Why would we decode the entire URI? If we know that user-data is encoded,
we can do urlPath.split('/') and grab the last component as the word, then
decode it to find the synonym.
Yeah, I've been thinking on this too. I have to give it a try probably.
> IIRC there have also been suggestions to deprecate and remove managed
resources, assuming they are less frequently used and that the more common way
of managing these is to push a new copy of the configset. I don't know how much
used these are - the fact that this bug is 8 years old hints that the feature
is not that popular?
Well, having an API for this is quite nice! It might not be very popular,
but overall, it works great. The issue with special characters isn't
significant; we discovered it after a couple of years of consistent operation.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
