[
https://issues.apache.org/jira/browse/OPENJPA-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120171#comment-18120171
]
ASF subversion and git services commented on OPENJPA-2989:
----------------------------------------------------------
Commit d5a3d3195a5b0cfc6d094af5cdc41ada275ab34d in openjpa's branch
refs/heads/master from Paulo Cristovão de Araújo Silva Filho
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=d5a3d3195 ]
Merge pull request #196 from apache/OPENJPA-2989
[OPENJPA-2989] Add a compatibility option to restore lazy query result lists
> Results always materialized, lazy ResultList behavior lost
> ----------------------------------------------------------
>
> Key: OPENJPA-2989
> URL: https://issues.apache.org/jira/browse/OPENJPA-2989
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 4.2.0
> Reporter: Maxim Solodovnik
> Priority: Major
> Fix For: 4.2.0
>
>
> Discussion thread:
> https://github.com/apache/openjpa/pull/144#discussion_r3683006506
> **(high)** Several assertions here (and in TestQueryTimeout) were inverted
> from "iterator must be invalid after query/EM close" to "iterator still works
> because results are now an ArrayList snapshot". Which JPA 3.2 clause requires
> this? More importantly, does this mean the lazy ResultList
> (openjpa.FetchBatchSize streaming results) is gone and results are always
> fully materialized? That would be a significant memory/perf behavior change
> deserving explicit discussion and release-noting, not just adjusted tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
