You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Kelvin Xu (JIRA)" <ji...@apache.org> on 2019/03/29 18:04:00 UTC

[jira] [Updated] (OAK-8167) Facet count with statistical mode should cover the case where whole facet results are not accessible

     [ https://issues.apache.org/jira/browse/OAK-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kelvin Xu updated OAK-8167:
---------------------------
    Issue Type: Improvement  (was: Bug)

> Facet count with statistical mode should cover the case where whole facet results are not accessible
> ----------------------------------------------------------------------------------------------------
>
>                 Key: OAK-8167
>                 URL: https://issues.apache.org/jira/browse/OAK-8167
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: indexing, lucene, query
>    Affects Versions: 1.6.16
>            Reporter: Kelvin Xu
>            Priority: Major
>              Labels: indexingWg
>
> With the statistical mode, facet count is updated proportionally to the percentage of accessible samples, which works for secured contents scattered across different facets. For edge case where the whole facet (results) is not accessible, the count still shows a number after the sampling percent is applied. Even if the number is small, user experience is misleading/inaccurate as nothing would return when the facet is clicked (applied as a query condition).
> For example, a ACLs/CUGs guarded "private" folder, in which all the assets are tagged with the same facet value. Non authorized user may still see this facet with a count but gets nothing when clicking on the facet.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)