[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407973#comment-13407973
]
Jukka Zitting commented on OAK-169:
-----------------------------------
bq. log entries
Using a timestamp property and queries based on that seem like a better way
than explicit ordering for handling these cases. Alternatively I'd say that a
date-based tree structure is indeed quite natural for a case like this as it
would make browsing and maintenance operations (like purging entries older than
a week, etc.) a lot easier than just a single flat list of entries.
bq. processing queue
Such queues typically remain within reasonable size bounds, right? I.e. you'd
expect to have up to thousands but not to millions of entries in such a queue.
Alternatively, a timestamp property would likely work well also in this case.
> Support orderable nodes
> -----------------------
>
> Key: OAK-169
> URL: https://issues.apache.org/jira/browse/OAK-169
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
> Reporter: Jukka Zitting
>
> There are JCR clients that depend on the ability to explicitly specify the
> order of child nodes. That functionality is not included in the MicroKernel
> tree model, so we need to implement it either in oak-core or oak-jcr using
> something like an extra (hidden) {{oak:childOrder}} property that records the
> specified ordering of child nodes. A multi-valued string property is probably
> good enough for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
