: Hmm, setting -Dfile.encoding=UTF-8 solves the problem. I have to now check
: which component of the application screws it up, but at the moment I do NOT
: believe it is related to Solrj.
You can use the "forbidden-apis" project to analyze your code and look for
uses of APIs that depend on the default file encoding, locale, charset,
etc...
https://github.com/policeman-tools/forbidden-apis
...this project started as an offshoot of build rules in
Lucene/Solr, precisely to help detect problems like the one you
are facing -- and it's used to analyze all Solr code, which is why i'm
pretty confident that no SolrJ code is mistakenly
parsing/converting/encoding your input -- allghough in theory it could be
a 3rd party library Solr uses. (Hardcoding the unicode string in your
java application and passing it as a solr param should help prove/disprove
that)
:
: On Fri, Aug 7, 2020 at 11:53 AM Jörn Franke <jornfra...@gmail.com> wrote:
:
: > Dear all,
: >
: > I have the following issues. I have a Solrj Client 8.6 (but it happens
: > also in previous versions), where I execute, for example, the following
: > query:
: > Jörn
: >
: > If I look into Solr Admin UI it finds all the right results.
: >
: > If I use Solrj client then it does not find anything.
: > Further, investigating in debug mode it seems that the URI to server gets
: > wrongly encoded.
: > Jörn becomes J%C3%83%C2%B6rn
: > It should become only J%C3%B6rn
: > any idea why this happens and why it add %83%C2 inbetween? Those do not
: > seem to be even valid UTF-8 characters
: >
: > I verified with various statements that I give to Solrj the correct
: > encoded String "Jörn"
: >
: > Can anyone help me here?
: >
: > Thank you.
: >
: > best regards
: >
:
-Hoss
http://www.lucidworks.com/
