[
https://issues.apache.org/jira/browse/OAK-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-9625:
--------------------------------
Summary: Support ordered index for first value of a multi-valued property,
node name, and path (was: Support ordered index for first value of a
multi-valued property, and path)
> Support ordered index for first value of a multi-valued property, node name,
> and path
> -------------------------------------------------------------------------------------
>
> Key: OAK-9625
> URL: https://issues.apache.org/jira/browse/OAK-9625
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Thomas Mueller
> Priority: Major
>
> Keyset pagination
> https://jackrabbit.apache.org/oak/docs/query/query-engine.html#Keyset_Pagination
> requires ordered indexing on a property.
> If all we have is a property "x", which is set on "nt:base" (or a similar
> node type), then an ordered index on the property "x" can be used for
> pagination. However, if the property is sometimes multi-valued, then it's not
> possible, because we don't support ordered indexes on multi-valued properties.
> If we have a property that is set on a mixin type (or primary node type),
> then the index can be much smaller, as we only need to index that node type.
> However, even here we need a property to do pagination. One option is to
> order by the lower case version of the name. However, this is quite strange.
> Also, the node name may not be unique, which complicates things further. It
> would be good if we can define an ordered index on the path itself (which is
> unique).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
