Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15743 ( https://hibernate.atlassian.net/browse/HHH-15743?atlOrigin=eyJpIjoiOWMyMj... ) Re: Querying with empty parameter list fails ( https://hibernate.atlassian.net/browse/HHH-15743?atlOrigin=eyJpIjoiOWMyMj... ) That’s new to me. Can you show me a reference where this is explicitly stated? Because this implies that nobody encourages this kind of usage. I’m sorry you based part of your application on something unspecified which just happened to work in this particular case, but like I wrote before, this kind of query is very inefficient. Don’t use that. Go the extra mile and implement proper conditional filtering. You don’t. I’d suggest everyone to use Spring Data Specification here for this purpose. @Repository public interface UserRepository extends JpaRepository<User, Long> { @Query("from User u " + "where COALESCE(:departments) is null or u.department in (:departments)") default List<User> findAllByOptionalDepartmentIn( @Param("departments") List<Department> departments, Sort sort) { return findAllByOptionalDepartmentIn( (root, query, cb) -> { return departments.isEmpty() ? null : root.get("department").in(departments) }, sort ); } List<User> findAllByOptionalDepartmentIn( Specification<User> spec, Sort sort); } ( https://hibernate.atlassian.net/browse/HHH-15743#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15743#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100210- sha1:eab5823 )