It seems the creation of a SearchQuery mutates a SearchSort by calling org.hibernate.search.backend.lucene.types.sort.comparatorsource.impl.LuceneFieldComparatorSource#setOriginalParentQuery (the comparator source being a component of the SearchSort).

Thus, if we create two queries with the same SearchSort instance, the second SearchQuery will have the final word on what gets passed to setOriginalParentQuery, and then executing the first SearchQuery will lead to unexpected results (since the sort uses the wrong Lucene query internally).

SearchSort should be immutable in order to avoid that.