[
https://issues.apache.org/jira/browse/SLING-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760936#comment-17760936
]
Julian Reschke edited comment on SLING-11799 at 8/31/23 1:46 PM:
-----------------------------------------------------------------
Turns out that the number of distinct names is not *that* interesting. What
would be needed is the (first) alias that has the most occurrences.
Assuming that aliases do not change that much, finding these during startup,
logging interesting findings, and throwing away the data structure should be
good enough.
was (Author: reschke):
Turns around that the number of distinct names is not *that* interesting. What
would be needed is the (first) alias that has the most occurrences.
Assuming that aliases do not change that much, finding these during startup,
logging interesting findings, and throwing away the data structure should be
good enough.
> use keyset pagination for sling:alias query
> -------------------------------------------
>
> Key: SLING-11799
> URL: https://issues.apache.org/jira/browse/SLING-11799
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
>
> Similar to what was done for vanity paths (SLING-11581), we should use keyset
> pagination for queries for sling:alias.
> This would work the same in principle, however we should keep in mind that -
> due to the different type of data - we may have way more duplicates, so in
> edge cases the pages might be bigger than expected. However, every size
> reduction of "results of a single query" should help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
