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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/12/12 14:37:01 UTC

[jira] [Closed] (OAK-5134) temporarily allow prefiltering test mode to be configured via an osgi config

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

Davide Giannella closed OAK-5134.
---------------------------------

Bulk close for 1.5.15

> temporarily allow prefiltering test mode to be configured via an osgi config
> ----------------------------------------------------------------------------
>
>                 Key: OAK-5134
>                 URL: https://issues.apache.org/jira/browse/OAK-5134
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: jcr
>    Affects Versions: 1.5.14
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Trivial
>             Fix For: 1.5.15
>
>
> The prefiltering feature (of ChangeProcessor) currently has a System.property "{{oak.observation.prefilteringTestMode}}" which allows turning on/off a so called _test mode_. In the test mode prefiltering is evaluated but its result is not applied. Instead of applying, the prefiltering result (include vs exclude) is compared to whether any event is actually delivered to the listener. If an event is delivered and prefiltering result is _exclude_ then a log.warn is issued.
> While generally the System.property mechanism is slightly suboptimal, in this case it makes testing in a broader (AEM) context more difficult. It would be useful to be able to temporarily (ie until before 1.6) have an osgi config to turn this feature on or off.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)