jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1996) Handle date values in the far future or prevent these from being persisted
Date Tue, 24 Mar 2009 20:33:50 GMT

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

Marcel Reutegger resolved JCR-1996.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0

Committed patch in revision: 758003

> 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.6.0
>
>         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.


Mime
View raw message