Hi,
On Wed, May 2, 2012 at 10:38 PM, Michael Dürig wrote:
> I noted however, that some of the files in
> /oak-core/src/main/java/org/apache/jackrabbit/mk/fs do not have the Apache
> copyright header. We should fix this first. I found these files by manual
> inspection but I guess the rat plugin s
Thanks Alex for preparing this!
I noted however, that some of the files in
/oak-core/src/main/java/org/apache/jackrabbit/mk/fs do not have the
Apache copyright header. We should fix this first. I found these files
by manual inspection but I guess the rat plugin should have found them
too. So
A candidate for the Jackrabbit Oak 0.2 release is available at:
http://people.apache.org/~alexparvulescu/oak/0.2/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-0.2/
The SHA1 checksum of the archive is
c89e141
Hi,
On Tue, Apr 24, 2012 at 2:17 PM, Alex Parvulescu
wrote:
> What would be nice is to attach an issue number to each item on this list,
> and mark it as to be fixed for 0.2 even if it is still unresolved.
> This way it is a lot easier to track the remaining work to be done.
Agreed, though at th
[
https://issues.apache.org/jira/browse/OAK-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated OAK-57:
-
Fix Version/s: (was: 0.2)
> Cleanup o.a.j.mk from oak-core
> --
>
>
[
https://issues.apache.org/jira/browse/OAK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266722#comment-13266722
]
Julian Reschke commented on OAK-6:
--
TCK status 2012-05-02: Tests: 1905, Errors: 228, Failures:
[
https://issues.apache.org/jira/browse/OAK-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg reassigned OAK-79:
Assignee: Stefan Guggisberg
> Copy operation misses some child nodes
>
[
https://issues.apache.org/jira/browse/OAK-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266647#comment-13266647
]
Jukka Zitting commented on OAK-56:
--
Where are we with this? Is there a particular place in th
[
https://issues.apache.org/jira/browse/OAK-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-72:
--
Summary: Implement JCR API (jsr 283, jsr 333) (was: Implement JCR API (jsr
283, jcr 333))
> Implement
[
https://issues.apache.org/jira/browse/OAK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266643#comment-13266643
]
Jukka Zitting commented on OAK-23:
--
bq. Thus our assumption that they never occur on Oak path
Hi,
[new thread, since this is a broader issue than OAK-80]
On Wed, May 2, 2012 at 4:50 PM, Thomas Mueller (JIRA) wrote:
> The question is how would you build an an efficient oak-core remoting, if
> every
> Node.setProperty requires a TCP/IP roundtrip, because it goes through oak-core
> and do
[
https://issues.apache.org/jira/browse/OAK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266612#comment-13266612
]
Julian Reschke commented on OAK-23:
---
Note that identifier paths can also occur in PATH-typed
[
https://issues.apache.org/jira/browse/OAK-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-81.
--
Resolution: Fixed
Fix Version/s: 0.2
Fixed at revision 1333068
> Remove offset and
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266605#comment-13266605
]
Thomas Mueller commented on OAK-80:
---
>> the long term goal
> ... Anyway, I don't see how tha
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266587#comment-13266587
]
Jukka Zitting commented on OAK-80:
--
bq. the long term goal
Ah yes, you're right. Anyway, I d
[
https://issues.apache.org/jira/browse/OAK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266574#comment-13266574
]
Julian Reschke commented on OAK-6:
--
TCK status 2012-05-01: Tests: 1905, Errors: 220, Failures:
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266541#comment-13266541
]
Thomas Mueller commented on OAK-80:
---
>> remoting between oak-jcr and oak-core
> I don't thin
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266538#comment-13266538
]
Stefan Guggisberg commented on OAK-80:
--
FWIW:
> Personally I'd rather see such batching
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266523#comment-13266523
]
Jukka Zitting commented on OAK-80:
--
OK, makes sense.
> Implement batched wri
Michael Dürig created OAK-81:
Summary: Remove offset and count parameters from
NodeState.getChildNodeEntries()
Key: OAK-81
URL: https://issues.apache.org/jira/browse/OAK-81
Project: Jackrabbit Oak
On 2.5.12 13:31, Jukka Zitting wrote:
Hi,
On Wed, May 2, 2012 at 1:17 PM, Michael Dürig wrote:
If no one objects, I'll remove these parameters and adapt KernelNodeState to
take care of lazy reading.
Sounds OK to me.
See https://issues.apache.org/jira/browse/OAK-81.
Michael
BR,
Jukka
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266515#comment-13266515
]
Jukka Zitting commented on OAK-80:
--
bq. remoting between oak-jcr and oak-core
I don't think
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266516#comment-13266516
]
Michael Dürig commented on OAK-80:
--
Yes this would be another option. However, I'd rather pus
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266510#comment-13266510
]
Thomas Mueller commented on OAK-80:
---
If we want to support an efficient remoting between the
Hi,
On Wed, May 2, 2012 at 1:17 PM, Michael Dürig wrote:
> If no one objects, I'll remove these parameters and adapt KernelNodeState to
> take care of lazy reading.
Sounds OK to me.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266506#comment-13266506
]
Jukka Zitting commented on OAK-80:
--
Personally I'd rather see such batching happening under t
[
https://issues.apache.org/jira/browse/OAK-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266503#comment-13266503
]
Michael Dürig commented on OAK-80:
--
Revision 1333010 adds new implementations for NodeStateBu
Michael Dürig created OAK-80:
Summary: Implement batched writing for KernelNodeStore
Key: OAK-80
URL: https://issues.apache.org/jira/browse/OAK-80
Project: Jackrabbit Oak
Issue Type: Improvement
Hi,
Is there a uses case for having offset and count parameters in
NodeState.getChildNodeEntries (package
org.apache.jackrabbit.oak.spi.state)? The only one I can see is to do
lazy reading from the Microkernel. This can however also be done
implicitly by the implementation of getChildNodeEnt
Michael Dürig created OAK-79:
Summary: Copy operation misses some child nodes
Key: OAK-79
URL: https://issues.apache.org/jira/browse/OAK-79
Project: Jackrabbit Oak
Issue Type: Bug
Compo
30 matches
Mail list logo
