[
https://issues.apache.org/jira/browse/OAK-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-5402:
---------------------------------
Fix Version/s: (was: 1.8)
> Lucene Ordered index should handle case where property defined as DATE is
> stored as LONG
> ----------------------------------------------------------------------------------------
>
> Key: OAK-5402
> URL: https://issues.apache.org/jira/browse/OAK-5402
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
>
> For ordered lucene indexes its required to define property type. In some
> cases its seen that a property which defined as {{date}} is stored as
> {{long}} which causes such nodes to be indexed partially.
> For example a property {{lastModified}} is normally defined as DATE. For some
> nodes the value is stored as LONG. Currently such nodes would be indexed
> partially i.e. the ordered property would not be indexed.
> {noformat}
> org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditor
> [/oak:index/versionStoreIndex] Ignoring ordered property. Could not convert
> property cq:lastModified of type LONG to type DATE for path
> /jcr:system/jcr:versionStorage/e4/ec/2b/e4ec2b45-c92b-4d05-9d56-0c5dee81860a/1.0/jcr:frozenNode/metaData
> {noformat}
> We can handle such cases by using the value as is instead of forcing it to
> convert to DATE
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
