xtenzQ commented on PR #1829:
URL: https://github.com/apache/solr/pull/1829#issuecomment-1709082973
@janhoy I'm not sure if I can improve my fix in some way.
Also, I apologize for the late reply, I was on the move.
--
This is an automated message from the Apache Git Service.
To res
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.
Ye
xtenzQ commented on PR #1829:
URL: https://github.com/apache/solr/pull/1829#issuecomment-1682193207
> @xtenzQ I saw your comment about "workaround", and are you aware of the
effort to roll out new "proper RESTful" api's for Solr? These new V2 apis use
the proper http verbs, so deleting a ma
xtenzQ commented on PR #1829:
URL: https://github.com/apache/solr/pull/1829#issuecomment-1681600877
@janhoy I've begun to question whether my current solution is more of a
workaround rather than an actual resolution that eliminates the problem.
To be honest, there are certain aspects
xtenzQ commented on PR #1829:
URL: https://github.com/apache/solr/pull/1829#issuecomment-1681450555
@janhoy I've begun to question whether my current solution is more of a
workaround rather than an actual solution.
I've been contemplating recently how to create a universal solution fo
xtenzQ commented on PR #1829:
URL: https://github.com/apache/solr/pull/1829#issuecomment-1669483513
> Also feel free to add a line to CHANGES.txt, giving yourself credit
Is it ok if I added this ticket under bug section?
--
This is an automated message from the Apache Git Service.
T
