My own addendum: I found outh the following circumstance:
* We have the same table on a development system and on a productive system. * On the development, the same query throws an error, but not so ond the productive system. * The development system's index is version 1.7, whilst the productive system's index is version 1.6. So, my question is: Can this make a difference? kr, Mag.phil. Robert Ehrenleitner, BEng. -- [cid:0836c166-bed8-4376-95f4-cd786f8b8815] Mag.phil. Robert Ehrenleitner, BEng. Web-Developer IT-Services | Application & Digitalization Services Hellbrunner Straße 34 | 5020 Salzburg | Austria Tel.: +43/(0)662/8044 - 6778 www.plus.ac.at<http://www.plus.ac.at> ________________________________ Von: ufuk yılmaz <uyil...@vivaldi.net.INVALID> Gesendet: Mittwoch, 2. April 2025 17:23 An: users@solr.apache.org <users@solr.apache.org> Betreff: Re: Solr returns confusing error message regarding copy-field [Sie erhalten nicht häufig E-Mails von uyil...@vivaldi.net.invalid. Weitere Informationen, warum dies wichtig ist, finden Sie unter https://aka.ms/LearnAboutSenderIdentification ] Copy field is just a directive that tells data should be copied from source field A to target field B, so “copy field” itself is not a field (think “copy” as a verb) The target field and source field are regular fields and can take all kinds of attributes like indexed=true or docValues=true So sorting or querying on a “copy field” is not logical as it is not a field. Source and target files can be queried/sorted -Ufuk — > On Apr 2, 2025, at 22:40, Ehrenleitner Robert Harald > <robert.ehrenleit...@plus.ac.at> wrote: > > title_str
