Does null precedence work on Page requests? Because its not working for me with version 3.2.1

Sort.Order sort = switch (direction != null ? direction : "") {
            case "asc" -> Sort.Order.asc(sortBy);
            case "desc" -> Sort.Order.desc(sortBy).nullsLast();
            default -> Sort.Order.asc("code");
        };

PageRequest pageRequest = PageRequest.of(
                alarmPageableFilter.getPageNumber(),
                alarmPageableFilter.getPageSize(),
                Sort.by(sort));

Page<Alarm> page = alarmRepository.findAll(getByFilter(alarmPageableFilter), pageRequest);

No, it's not working with 3.2.1 because the JPA spec level is at 3.1. Starting with JPA 3.2, the API will specify null precedence (see https://projects.eclipse.org/projects/ee4j.jpa/releases/3.2)

I have the same issue too. Dont understand why it's happen

@mp911de and @christophstrobl - would you guys know when the issue that @Nendanfito explained here will be fixed?

Does null precedence work on Page requests? Because its not working for me with version 3.2.1

Sort.Order sort = switch (direction != null ? direction : "") {
            case "asc" -> Sort.Order.asc(sortBy);
            case "desc" -> Sort.Order.desc(sortBy).nullsLast();
            default -> Sort.Order.asc("code");
        };

PageRequest pageRequest = PageRequest.of(
                alarmPageableFilter.getPageNumber(),
                alarmPageableFilter.getPageSize(),
                Sort.by(sort));

Page<Alarm> page = alarmRepository.findAll(getByFilter(alarmPageableFilter), pageRequest);

Did you find a workaround?

@emaranga I configured it for spring in general in the application.yaml:

spring:
  jpa:
    properties:
      hibernate:
        order_by:
          default_null_ordering: last

With that solution all the querys made by jpa will return nulls last, in case you don't want it you have to made a nativeQuery.