Hello Marco Perazzo,

Thanks for this report.

First, let me warn you that working directly with the document ID is not recommended; there are known issues with making it sortable in particular. A safer approach would be to use an additional field and make that field numeric and sortable. I think you could even name the additional field "id" an rename the document ID to something like "_id_internal" (using @DocumentId(name = "_id_internal")).

Now, I tried to reproduce the issue in a test case (see this branch, this file in particular), but I couldn't: everything seems to work fine. There may be some specific configuration in your application that you didn't mention.

Do you think you could provide a test case demonstrating the issue? You can find test case templates here: https://github.com/hibernate/hibernate-test-case-templates/tree/master/search
There's a README, but don't hesitate to ask if you have questions about setting up the test case.

Thanks,
Yoann