[
https://issues.apache.org/jira/browse/OAK-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406910#comment-13406910
]
Dominique Pfister edited comment on OAK-114 at 7/5/12 8:30 AM:
---
[
https://issues.apache.org/jira/browse/OAK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406581#comment-13406581
]
Stefan Guggisberg edited comment on OAK-167 at 7/5/12 8:44 AM:
---
Hi,
I agree with Felix. I don't currently see a need for Sling to bypass the
JCR API. If that would be needed, there is something wrong with the JCR
API or the JCR implementation.
About indexing:
Another potential Sling extension would be a custom Oak index provider
for optimizing the kinds
On Thu, Jul 5, 2012 at 12:19 PM, Thomas Mueller muel...@adobe.com wrote:
About indexing:
Another potential Sling extension would be a custom Oak index provider
for optimizing the kinds of queries Sling uses.
I'm not sure what you mean here. I don't see Sling having it's own index
Hi,
On Wed, Jul 4, 2012 at 5:43 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Wed, Jul 4, 2012 at 5:35 PM, Stefan Guggisberg
stefan.guggisb...@gmail.com wrote:
On Wed, Jul 4, 2012 at 2:37 PM, Michael Dürig mdue...@apache.org wrote:
- HTTP bindings (OAK-103, OAK-104)
* Provide
[
https://issues.apache.org/jira/browse/OAK-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406997#comment-13406997
]
Jukka Zitting commented on OAK-114:
---
bq. The javadoc is possibly not clear enough: a
Hi,
I'm not sure what you mean here. I don't see Sling having it's own index
*mechanism*. Probably Sling will need specific indexes, but that's just
configuration, and not implementation (code)...
Being able to integrate totally different indexing mechanisms can be
useful if Oak can provide
[
https://issues.apache.org/jira/browse/OAK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406999#comment-13406999
]
Jukka Zitting commented on OAK-167:
---
bq. wouldn't that ideally be the transient space, i.e.
[
https://issues.apache.org/jira/browse/OAK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407028#comment-13407028
]
Stefan Guggisberg commented on OAK-167:
---
IMO we have no choice but buffer transient
[
https://issues.apache.org/jira/browse/OAK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407031#comment-13407031
]
Jukka Zitting commented on OAK-167:
---
bq. IMO we have no choice but buffer transient changes
[
https://issues.apache.org/jira/browse/OAK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407038#comment-13407038
]
Stefan Guggisberg commented on OAK-167:
---
bq. That's a separate issue (OAK-162 as you
Jukka Zitting created OAK-168:
-
Summary: Basic JCR VersionManager support
Key: OAK-168
URL: https://issues.apache.org/jira/browse/OAK-168
Project: Jackrabbit Oak
Issue Type: Bug
Hi,
The vote passes as follows:
+1 Jukka Zitting
+1 Julian Reschke
+1 Michael Dürig
+1 Alex Parvulescu
Thanks for voting!
I'll push the release out.
alex
On Wed, Jul 4, 2012 at 11:21 AM, Michael Dürig mdue...@apache.org wrote:
Please vote on releasing this package as Apache
[
https://issues.apache.org/jira/browse/OAK-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller reassigned OAK-155:
--
Assignee: Thomas Mueller
Query: limited support for the deprecated JCR 1.0 query language
[
https://issues.apache.org/jira/browse/OAK-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407201#comment-13407201
]
Dominique Pfister commented on OAK-114:
---
bq.{quote} If we are keeping track of when a
Jukka Zitting created OAK-169:
-
Summary: Support orderable nodes
Key: OAK-169
URL: https://issues.apache.org/jira/browse/OAK-169
Project: Jackrabbit Oak
Issue Type: New Feature
16 matches
Mail list logo
