You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2010/01/15 23:28:54 UTC
[jira] Created: (JCR-2468) Indexing configuration not refreshed
after node type registration
Indexing configuration not refreshed after node type registration
-----------------------------------------------------------------
Key: JCR-2468
URL: https://issues.apache.org/jira/browse/JCR-2468
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Affects Versions: 2.0-beta5, 2.0-beta4, 2.0-beta3, 2.0-beta1, 2.0-alpha11, 2.0-alpha9, 2.0-alpha8, 2.0-alpha7, 2.0-alpha4, 2.0-alpha3, 2.0-alpha1, 1.6.0, 1.5.7, 1.5.6, 1.5.5, 1.5.4, 1.5.3, 1.5.2, 1.5.0, core-1.4.11, core 1.4.10, core 1.4.9, core 1.4.7, core 1.4.8, core 1.4.6, core 1.4.5, core 1.4.4, core 1.4.3, core 1.4.2, core 1.4.1, 1.4, 1.5.8, 1.6.1, 2.0-beta6
Reporter: Marcel Reutegger
The indexing configuration has internal caches that speed up node type matches. Those caches are not updated on new node type registration and newly registered node types are not properly resolved when index-rules are checked.
See also test case in attached patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2468) Indexing configuration not refreshed
after node type registration
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-2468:
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Status: Resolved (was: Patch Available)
Applied patch to trunk in revision: 900314 and merged into 2.0 branch in revision: 900317
> Indexing configuration not refreshed after node type registration
> -----------------------------------------------------------------
>
> Key: JCR-2468
> URL: https://issues.apache.org/jira/browse/JCR-2468
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4, core 1.4.1, core 1.4.2, core 1.4.3, core 1.4.4, core 1.4.5, core 1.4.6, core 1.4.8, core 1.4.7, core 1.4.9, core 1.4.10, core-1.4.11, 1.5.0, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.6.0, 1.6.1, 2.0-alpha1, 2.0-alpha3, 2.0-alpha4, 2.0-alpha7, 2.0-alpha8, 2.0-alpha9, 2.0-alpha11, 2.0-beta1, 2.0-beta3, 2.0-beta4, 2.0-beta5, 2.0-beta6
> Reporter: Marcel Reutegger
> Fix For: 2.0.0
>
> Attachments: JCR-2468.patch
>
>
> The indexing configuration has internal caches that speed up node type matches. Those caches are not updated on new node type registration and newly registered node types are not properly resolved when index-rules are checked.
> See also test case in attached patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2468) Indexing configuration not refreshed
after node type registration
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-2468:
----------------------------------
Status: Patch Available (was: Open)
> Indexing configuration not refreshed after node type registration
> -----------------------------------------------------------------
>
> Key: JCR-2468
> URL: https://issues.apache.org/jira/browse/JCR-2468
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.0-beta5, 2.0-beta4, 2.0-beta3, 2.0-beta1, 2.0-alpha11, 2.0-alpha9, 2.0-alpha8, 2.0-alpha7, 2.0-alpha4, 2.0-alpha3, 2.0-alpha1, 1.6.0, 1.5.7, 1.5.6, 1.5.5, 1.5.4, 1.5.3, 1.5.2, 1.5.0, core-1.4.11, core 1.4.10, core 1.4.9, core 1.4.7, core 1.4.8, core 1.4.6, core 1.4.5, core 1.4.4, core 1.4.3, core 1.4.2, core 1.4.1, 1.4, 1.5.8, 1.6.1, 2.0-beta6
> Reporter: Marcel Reutegger
> Attachments: JCR-2468.patch
>
>
> The indexing configuration has internal caches that speed up node type matches. Those caches are not updated on new node type registration and newly registered node types are not properly resolved when index-rules are checked.
> See also test case in attached patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2468) Indexing configuration not refreshed
after node type registration
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-2468:
----------------------------------
Attachment: JCR-2468.patch
Test case and proposed fix.
> Indexing configuration not refreshed after node type registration
> -----------------------------------------------------------------
>
> Key: JCR-2468
> URL: https://issues.apache.org/jira/browse/JCR-2468
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4, core 1.4.1, core 1.4.2, core 1.4.3, core 1.4.4, core 1.4.5, core 1.4.6, core 1.4.8, core 1.4.7, core 1.4.9, core 1.4.10, core-1.4.11, 1.5.0, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.6.0, 1.6.1, 2.0-alpha1, 2.0-alpha3, 2.0-alpha4, 2.0-alpha7, 2.0-alpha8, 2.0-alpha9, 2.0-alpha11, 2.0-beta1, 2.0-beta3, 2.0-beta4, 2.0-beta5, 2.0-beta6
> Reporter: Marcel Reutegger
> Attachments: JCR-2468.patch
>
>
> The indexing configuration has internal caches that speed up node type matches. Those caches are not updated on new node type registration and newly registered node types are not properly resolved when index-rules are checked.
> See also test case in attached patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.