You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/04/22 16:34:47 UTC
[jira] Updated: (JCR-1996) Handle date values in the far future or
prevent these from being persisted
[ https://issues.apache.org/jira/browse/JCR-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1996:
-------------------------------
Fix Version/s: (was: 1.6.0)
1.5.5
Merged to the 1.5 branch in revision 767539.
> Handle date values in the far future or prevent these from being persisted
> --------------------------------------------------------------------------
>
> Key: JCR-1996
> URL: https://issues.apache.org/jira/browse/JCR-1996
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: indexing, jackrabbit-core, jackrabbit-jcr-commons
> Affects Versions: 1.5.3
> Reporter: Martijn Hendriks
> Fix For: 1.5.5
>
> Attachments: JCR-1996.patch, JCR-1996.patch
>
>
> Setting a date property with a value in the far future (e.g., the year 20009) and saving the session causes the index component to throw an exception (see the DateField#timeToString method). Furthermore, when the repository is restarted, the properties' value cannot be retrieved anymore because of a ValueFormatException caused by an empty value. Restarting the repository with an empty search index does not work because indexing fails. I haven't looked into the effect on queries.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.