[jira] Updated: (OPENJPA-175) Eager selects by PagingResultObjectProvider may not use the FetchBatchSize
[ https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivasa updated OPENJPA-175: -- Attachment: InExpression-Diff.txt > Eager selects by PagingResultObjectProvider may not use the FetchBatchSize > -- > > Key: OPENJPA-175 > URL: https://issues.apache.org/jira/browse/OPENJPA-175 > Project: OpenJPA > Issue Type: Bug >Affects Versions: 0.9.0, 0.9.6 >Reporter: Srinivasa > Attachments: InExpression-Diff.txt, OPENJPA-175-patch.txt, > OPENJPA-175-patch.txt > > > The PagingResultObjectProvider during initialization does checks to determine > the appropriate pageSize. While this logic caps the size to 50 and addresses > determining an appropriate page size, it doesn't always conform to the set > batch size. For example with the size being 1000 and FetchBatchSize set to > say 500, the page size is determined to be 50 resulting in eager selects > happening in batches of 50 when the user expects it to be in batches of 500. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-175) Eager selects by PagingResultObjectProvider may not use the FetchBatchSize
[ https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivasa updated OPENJPA-175: -- 1 - Yes, was planning to do it as a separate JIRA given that it directly does not concern the issue raised here, however I will include it here since we are introducing the in-clause limit in the DBDictionary for this fix. 2 - Looks fine to me, except for the minor issue that in the (size <= batch * 2) case we will not be adhering to the FetchBatchSize for pageSize in that the first in-clause query will be for lesser than the FetchBatchSize number of entries, however we will still endup running the same number of in-clause queries - 2. > Eager selects by PagingResultObjectProvider may not use the FetchBatchSize > -- > > Key: OPENJPA-175 > URL: https://issues.apache.org/jira/browse/OPENJPA-175 > Project: OpenJPA > Issue Type: Bug >Affects Versions: 0.9.0, 0.9.6 >Reporter: Srinivasa > Attachments: OPENJPA-175-patch.txt, OPENJPA-175-patch.txt > > > The PagingResultObjectProvider during initialization does checks to determine > the appropriate pageSize. While this logic caps the size to 50 and addresses > determining an appropriate page size, it doesn't always conform to the set > batch size. For example with the size being 1000 and FetchBatchSize set to > say 500, the page size is determined to be 50 resulting in eager selects > happening in batches of 50 when the user expects it to be in batches of 500. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-175) Eager selects by PagingResultObjectProvider may not use the FetchBatchSize
[ https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivasa Segu updated OPENJPA-175: --- Attachment: OPENJPA-175-patch.txt Patch with fixes to address the FetchBatchSize values of -1, 0. For FetchBatchSize being 0 or negative value other than -1 uses the earlier logic of determining a pageSize capped by 50 based on size. > Eager selects by PagingResultObjectProvider may not use the FetchBatchSize > -- > > Key: OPENJPA-175 > URL: https://issues.apache.org/jira/browse/OPENJPA-175 > Project: OpenJPA > Issue Type: Bug >Affects Versions: 0.9.0, 0.9.6 >Reporter: Srinivasa Segu > Attachments: OPENJPA-175-patch.txt, OPENJPA-175-patch.txt > > > The PagingResultObjectProvider during initialization does checks to determine > the appropriate pageSize. While this logic caps the size to 50 and addresses > determining an appropriate page size, it doesn't always conform to the set > batch size. For example with the size being 1000 and FetchBatchSize set to > say 500, the page size is determined to be 50 resulting in eager selects > happening in batches of 50 when the user expects it to be in batches of 500. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-175) Eager selects by PagingResultObjectProvider may not use the FetchBatchSize
[ https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivasa Segu updated OPENJPA-175: --- Attachment: OPENJPA-175-patch.txt > Eager selects by PagingResultObjectProvider may not use the FetchBatchSize > -- > > Key: OPENJPA-175 > URL: https://issues.apache.org/jira/browse/OPENJPA-175 > Project: OpenJPA > Issue Type: Bug >Affects Versions: 0.9.0, 0.9.6 >Reporter: Srinivasa Segu > Attachments: OPENJPA-175-patch.txt > > > The PagingResultObjectProvider during initialization does checks to determine > the appropriate pageSize. While this logic caps the size to 50 and addresses > determining an appropriate page size, it doesn't always conform to the set > batch size. For example with the size being 1000 and FetchBatchSize set to > say 500, the page size is determined to be 50 resulting in eager selects > happening in batches of 50 when the user expects it to be in batches of 500. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
