You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2026/08/11 14:57:00 UTC
[jira] [Commented] (OAK-12343) Document (and test) that ORDER BY on a type=Date ordered property fails when values aren't valid dates
[ https://issues.apache.org/jira/browse/OAK-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103709#comment-18103709 ]
Julian Reschke commented on OAK-12343:
--------------------------------------
Exactly how would that kind of inconsistency ever get into a lucene index...?
> Document (and test) that ORDER BY on a type=Date ordered property fails when values aren't valid dates
> ------------------------------------------------------------------------------------------------------
>
> Key: OAK-12343
> URL: https://issues.apache.org/jira/browse/OAK-12343
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Anton Hosgood
> Priority: Major
>
> An ordered Lucene property index declared with type=Date only works if every value is a valid ISO-8601 date. Values that aren't (a non-ISO timestamp, or a plain string on some nodes) aren't indexed as dates, so ORDER BY on the property either returns the wrong order or — if the query relies on that property to select nodes — no results at all. type=String (or leaving type unset, or order by lower(...)) works instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)