You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Brian Moseley (JIRA)" <ji...@apache.org> on 2006/01/11 22:13:20 UTC
[jira] Created: (JCR-299) errors in text filters can cause indexing
to fail without warning the client
errors in text filters can cause indexing to fail without warning the client
----------------------------------------------------------------------------
Key: JCR-299
URL: http://issues.apache.org/jira/browse/JCR-299
Project: Jackrabbit
Type: Bug
Components: query
Versions: 1.0
Reporter: Brian Moseley
i've opened this issue to track the discussion at <http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/5086>. briefly, exceptions thrown by text filters are logged and swallowed by jackrabbit; there's no way for a text filter to signal to the jcr client that indexing failed.
some solutions have been proposed, including throwing an unchecked exception, which doesn't allow jackrabbit to maintain transactional integrity, and giving filters veto power over the observed repository operation. depending on the difficulty of the solution that is eventually determined to be correct, it may be sufficient for 1.0 to document the issue and perhaps improve the warning/error logging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-299) errors in text filters can cause indexing
to fail without warning the client
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-299?page=all ]
Jukka Zitting updated JCR-299:
------------------------------
Version: 1.0
> errors in text filters can cause indexing to fail without warning the client
> ----------------------------------------------------------------------------
>
> Key: JCR-299
> URL: http://issues.apache.org/jira/browse/JCR-299
> Project: Jackrabbit
> Type: Bug
> Components: query
> Versions: 0.9, 1.0
> Reporter: Brian Moseley
> Fix For: 1.1
>
> i've opened this issue to track the discussion at <http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/5086>. briefly, exceptions thrown by text filters are logged and swallowed by jackrabbit; there's no way for a text filter to signal to the jcr client that indexing failed.
> some solutions have been proposed, including throwing an unchecked exception, which doesn't allow jackrabbit to maintain transactional integrity, and giving filters veto power over the observed repository operation. depending on the difficulty of the solution that is eventually determined to be correct, it may be sufficient for 1.0 to document the issue and perhaps improve the warning/error logging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-299) errors in text filters can cause indexing
to fail without warning the client
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-299?page=all ]
Jukka Zitting updated JCR-299:
------------------------------
Fix Version: 1.0
Version: 0.9
(was: 1.0)
> errors in text filters can cause indexing to fail without warning the client
> ----------------------------------------------------------------------------
>
> Key: JCR-299
> URL: http://issues.apache.org/jira/browse/JCR-299
> Project: Jackrabbit
> Type: Bug
> Components: query
> Versions: 0.9
> Reporter: Brian Moseley
> Fix For: 1.0
>
> i've opened this issue to track the discussion at <http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/5086>. briefly, exceptions thrown by text filters are logged and swallowed by jackrabbit; there's no way for a text filter to signal to the jcr client that indexing failed.
> some solutions have been proposed, including throwing an unchecked exception, which doesn't allow jackrabbit to maintain transactional integrity, and giving filters veto power over the observed repository operation. depending on the difficulty of the solution that is eventually determined to be correct, it may be sufficient for 1.0 to document the issue and perhaps improve the warning/error logging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-299) errors in text filters can cause indexing
to fail without warning the client
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-299?page=all ]
Jukka Zitting updated JCR-299:
------------------------------
Fix Version: 1.1
(was: 1.0)
> errors in text filters can cause indexing to fail without warning the client
> ----------------------------------------------------------------------------
>
> Key: JCR-299
> URL: http://issues.apache.org/jira/browse/JCR-299
> Project: Jackrabbit
> Type: Bug
> Components: query
> Versions: 0.9
> Reporter: Brian Moseley
> Fix For: 1.1
>
> i've opened this issue to track the discussion at <http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/5086>. briefly, exceptions thrown by text filters are logged and swallowed by jackrabbit; there's no way for a text filter to signal to the jcr client that indexing failed.
> some solutions have been proposed, including throwing an unchecked exception, which doesn't allow jackrabbit to maintain transactional integrity, and giving filters veto power over the observed repository operation. depending on the difficulty of the solution that is eventually determined to be correct, it may be sufficient for 1.0 to document the issue and perhaps improve the warning/error logging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira