[JCR-1996] Handle date values in the far future or prevent these from being persisted

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.3
• Fix Version/s: 1.5.5
• Component/s: indexing, jackrabbit-core, jackrabbit-jcr-commons
• Assignee: Unassigned
• Reporter: Martijn Hendriks
• Created: 24/Feb/09 13:10
• Updated: 09/Oct/09 07:34
• Resolved: 24/Mar/09 20:33

Description

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.

Issue Links

• is duplicated by: JCR-2350 Indexing node when date time is too late for lucene