[
https://issues.apache.org/jira/browse/CLEREZZA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Spicar updated CLEREZZA-678:
-----------------------------------
Description:
the findResources methods should support pagination by extending the interface
with (from, to) arguments. From is inclusive, to is exclusive.
Background: Currently the idea of the maxhits parameter in GraphIndexer has
been misunderstood. It can be used to support pagination in this manner:
First get results from 0-20 with maxhits 20. Then the user wants to see results
from 20-40, so the same IndexSearcher can be used with maxhits set to 40.
Because the IndexSearcher already holds results 0-19 in memory, only results
20-39 are loaded from the index.
was:
the findResources methods should support pagination by extending the interface
with (from, to) arguments. From is inclusive, to is exclusive.
Background: Currently the idea of the maxhits parameter in GraphIndexer has
been misunderstood. It can be used to support pagination in this manner:
First get results from 0-20 with maxhits 20. Then the user wants to see results
from 20-40, so the same IndexSearcher can be used with maxhits set to 40.
Because the IndexSearcher already holds results 0-19 in memory, only results
20-39 are loaded from the index.
Summary: Extend GraphIndexer interface to support pagination (was:
Extend ResourceFinder and GraphIndexer interfaces to support pagination)
> Extend GraphIndexer interface to support pagination
> ---------------------------------------------------
>
> Key: CLEREZZA-678
> URL: https://issues.apache.org/jira/browse/CLEREZZA-678
> Project: Clerezza
> Issue Type: Improvement
> Affects Versions: 0.2-incubating
> Reporter: Daniel Spicar
> Assignee: Daniel Spicar
> Priority: Minor
> Labels: cris, pagination
>
> the findResources methods should support pagination by extending the
> interface with (from, to) arguments. From is inclusive, to is exclusive.
> Background: Currently the idea of the maxhits parameter in GraphIndexer has
> been misunderstood. It can be used to support pagination in this manner:
> First get results from 0-20 with maxhits 20. Then the user wants to see
> results from 20-40, so the same IndexSearcher can be used with maxhits set to
> 40. Because the IndexSearcher already holds results 0-19 in memory, only
> results 20-39 are loaded from the index.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
