You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (Created) (JIRA)" <ji...@apache.org> on 2011/12/12 13:54:30 UTC
[jira] [Created] (JCR-3178) Improve error messages for index
aggregates
Improve error messages for index aggregates
-------------------------------------------
Key: JCR-3178
URL: https://issues.apache.org/jira/browse/JCR-3178
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: indexing
Reporter: Alex Parvulescu
Assignee: Alex Parvulescu
Priority: Trivial
In the case where an index aggregate fails because of a node that doesn't exist the logged warn messages contain a full stack-trace.
Besides the fact that this can be misleading (you may think that there's something wrong that you need to fix right away) it is also borderline useless.
The desired behavior would be to just log an "info" message mentioning that a certain node was skipped, similar to what the SeachManager does.
--
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
[jira] [Resolved] (JCR-3178) Improve error messages for index
aggregates
Posted by "Alex Parvulescu (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu resolved JCR-3178.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.3.6
Fixed in revision 1213249.
> Improve error messages for index aggregates
> -------------------------------------------
>
> Key: JCR-3178
> URL: https://issues.apache.org/jira/browse/JCR-3178
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: indexing
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Priority: Trivial
> Fix For: 2.3.6
>
>
> In the case where an index aggregate fails because of a node that doesn't exist the logged warn messages contain a full stack-trace.
> Besides the fact that this can be misleading (you may think that there's something wrong that you need to fix right away) it is also borderline useless.
> The desired behavior would be to just log an "info" message mentioning that a certain node was skipped, similar to what the SeachManager does.
--
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