You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Paul Ramirez (JIRA)" <ji...@apache.org> on 2012/08/30 17:21:07 UTC
[jira] [Commented] (OODT-216) Improve speed of pagination in
DataSourceCatalog by using lastIDs rather than scrollable cursors
[ https://issues.apache.org/jira/browse/OODT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445010#comment-13445010 ]
Paul Ramirez commented on OODT-216:
-----------------------------------
Instead of last id we could go with last reference as the lucene implementation is not guaranteed to have sorted ids but could use the product received time. In addition we would likely need 2 placeholders so that previous page can be easily supported. This will affect the serde for a product page so the implementations should be written to be resilient (i.e. fall back to current behavior).
> Improve speed of pagination in DataSourceCatalog by using lastIDs rather than scrollable cursors
> ------------------------------------------------------------------------------------------------
>
> Key: OODT-216
> URL: https://issues.apache.org/jira/browse/OODT-216
> Project: OODT
> Issue Type: Improvement
> Components: file manager
> Environment: from JPL's internal JIRA
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.5
>
>
> Currently, the filemgr's DataSourceCatalog leverages scrollable record cursor result sets to page over the returned results from an underlying JDBC database. With many records to page over (on the orders of 100s of 1000s), this operation is somewhat slow. I think that the speed of the operation could be improved using a filter criteria of e.g., taking the last ID of an ordered product list, and then using that as a filter criteria to define the starting point for paging, not bothering with scrollable cursors.
> This patch will provide such a capability as a configurable option for the DataSourceCatalog.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira