Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Pagination ignored on collection fetch join: Add the ability to throw an exception instead of loggin a warn

Description

When we query with pagination while join fetching a collection, pagination is ignored.

Currently the only way to know that it happens is a log of level warn.

In my case, I want a runtime exception to be thrown, because we can't let this behaviour happens in production.

It would be great to have a configuration flag that would enable the exception throw.

Activity

Show:

Former user January 30, 2018 at 12:41 AM

Fixed in 5.2 branch as well.

Former user January 29, 2018 at 11:34 PM

The commit that fixes this issue is: https://github.com/hibernate/hibernate-orm/commit/b711e14a6c1897ae95263eed21e697644b876489

That commit message incorrectly mentions HHH-10294.

Steve Ebersole December 18, 2017 at 2:26 PM

Applied upstream (master - 5.3). Thanks!

Steve Ebersole December 18, 2017 at 2:26 PM

This might be one to backport

Réda Housni Alaoui December 17, 2017 at 6:52 PM

Thanks for reopening the issue.

I created a new PR.
As discussed with , I made a more generic setting called FAIL_ON_INTENSIVE_IN_MEMORY_OPERATION to avoid the multiplication of settings.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created July 21, 2015 at 5:17 PM
Updated January 30, 2018 at 12:41 AM
Resolved January 30, 2018 at 12:41 AM
Configure