Re: Using oak run to compact older versions

Hi Roy Looking at https://jackrabbit.apache.org/oak/docs/nodestore/segment/changes.html, there don't seem to be any changes in the storage format of the TAR segment store. Therefore, I would expect no issues. I may be missing something, however. Regards Julian On Mon, Jun 17, 2024 at 12:47 PM

Re: Tarball Compaction Performance Issue

Hi Andreas Without looking at any more detail, I noticed that in your invocation I believe the flag name is misspelled: "—trheads=16" should probably be "—threads=16", unless it is misspelled in the implementation. Please confirm that this is NOT the issue. Thanks! Regards Julian On Fri, May

Re: VOTE: Migrate from Subversion to Git

[X] +1, migrate Jackrabbit to Git Regards Julian On Thu, Oct 12, 2023 at 6:57 AM Julian Reschke wrote: > > On 12.10.2023 06:55, Julian Reschke wrote: > > On 11.10.2023 19:58, Konrad Windszus wrote: > >> ... > > > > [X] +1, migrate Jackrabbit to Git > > > > Best regards, Julian > > ...and when

Please review fix for GC on SegmentStore setup with SplitPersistence

Hello I would appreciate a review of PR #665 [0], which fixes OAK-9897 [1]. When running GC on a SegmentStore setup with SplitPersistence, it happens regularly that the tar archives of the "read-only" part of the persistence are identified for removal during the "cleanup" phase. However, these

Intent to backport OAK-9785

Hello I intend to backport "OAK-9785 - Tar SegmentStore can be corrupted during compaction" to the 1.22 branch. The fix hardens TAR compaction by aborting it cleanly not only when an IOException is caught, but also when any other Throwable is caught. Let me know if you have any concerns.

Re: [VOTE] Release Apache Jackrabbit 2.16.10

[X] +1 Release this package as Apache Jackrabbit 2.16.10 ...where... [INFO] Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) [INFO] OS name: "mac os x", version: "12.4", arch: "x86_64", family: "mac" [INFO] Java version: 11.0.14, vendor: Oracle Corporation, runtime:

OAK-9896 - Running unit-tests in IntelliJ dos not work

Hi I am having issues when running unit-tests within Intellij IDEA. I can work around the issue, but it's a bit cumbersome. Therefore I would like to apply the change proposed in PR #664 [0], which addresses OAK-9896 [1]. Do others experience the same problem running unit-tests in Intellij? Does

Plan to merge changes for OAK-9888 - Support more flexible SplitPersistence setups via OSGi

Hi I am planning to merge PR #663 [0] on Wednesday. The changes address OAK-9888 [1] and are intended to allow more flexibility when creating a SplitPersistence. They affect the segment-tar and the segment-azure modules. Please let me know if you see any issues with this change. Regards Julian

Re: Outdated 1.22 branch

Hi Andrei I assume you would need to adjust the SCM Info in the pom of the "1.22" branch in Git (compare with the pom in "trunk" branch). The SVN branches are dead after migration to Git AFAIK. I don't know if other adjustments are required. Konrad would likely know. Regards Julian On Wed, Jul

Re: Adjustments of check-release.sh for multi module releases

Hi Combining the empty local repo with a fallback to the "full" local repo can speed things up a lot. I have used this strategy in the past to "fill" minimal customer-specific local repos to enable offline work. That requires a profile and thus a settings.xml, but that should all be scriptable I

Re: [Proposal] Feature toggles

Hi Marcel On Tue, Jul 7, 2020 at 12:02 PM Marcel Reutegger wrote: > > Hi, > > Thanks for the feedback Julian. > > On 07.07.20, 10:45, "Julian Sedding" wrote: > > I'm not sure about the aspect of the implementation, that FeatureToggle > > is Closeab

Re: [Proposal] Feature toggles

Hi Marcel, I think the API is elegant. Short of running "feature" code in a closure, a "try with resource" block encourages developers to clearly delimit the block of code that is subject to the feature toggle, hopefully resulting in readable code. I'm not sure about the aspect of the

Re: Query ordered by node name

Or alternatively try [function = "fn:name()"], i.e. with the brackets "()". Regards Julian On Tue, May 19, 2020 at 10:57 AM Julian Sedding wrote: > > Hi Jorge > > You could try the Oak Index Definition Generator. > > http://oakutils.appspot.com/generate/

Re: Query ordered by node name

Hi Jorge You could try the Oak Index Definition Generator. http://oakutils.appspot.com/generate/index FWIW, in the "name" property node it sets [name = ":name"] instead of [function = "fn:name"]. I don't know if that makes a difference and which is better, if any. Regards Julian On Mon, May

Re: Versionable node deletion

Hi Jorge If you're looking at reclaiming disk space from "orphaned" binaries, you likely need Blob Garbage Collection: https://jackrabbit.apache.org/oak/docs/plugins/blobstore.html#Blob_Garbage_Collection Regards Julian On Mon, Feb 24, 2020 at 3:58 PM jorgeeflorez . wrote: > > Hi Marco, > I

Re: New Jackrabbit Committer: Mohit Kataria

Welcome Mohit! Regards Julian On Wed, Aug 14, 2019 at 3:25 PM Woonsan Ko wrote: > > Welcome, Mohit! > > Cheers, > > Woonsan > > On Wed, Aug 14, 2019 at 2:31 AM Tommaso Teofili > wrote: > > > > Welcome to the team Mohit! > > > > Regards, > > Tommaso > > > > On Thu, 8 Aug 2019 at 08:33, Marcel

Re: New Jackrabbit Committer: Nitin Gupta

Welcome Nitin! Regards Julian On Wed, Aug 14, 2019 at 3:24 PM Woonsan Ko wrote: > > Welcome, Nitin! > > Cheers, > > Woonsan > > On Wed, Aug 14, 2019 at 2:30 AM Tommaso Teofili > wrote: > > > > Welcome to the team Nitin! > > > > Regards, > > Tommaso > > > > On Thu, 8 Aug 2019 at 08:31, Marcel

Re: New Jackrabbit Committer: Dominik Süß

Welcome, Dominik! Regards Julian On Thu, Jul 25, 2019 at 5:17 PM Dominik Süß wrote: > > Hello everyone, > > Like Konrad I wanted to thank a lot for the invitation. > > > Here a short version about my own background. I started working as Integrator > for AEM/CQ and that way getting in touch

Re: New Jackrabbit Committer: Konrad Windszus

Welcome Konrad! Regards Julian On Thu, Jul 25, 2019 at 4:02 PM Woonsan Ko wrote: > > Welcome, Konrad! > > Cheers, > > Woonsan > > On Wed, Jul 24, 2019 at 10:11 AM Konrad Windszus wrote: > > > > Hi everyone, > > thanks a lot for having invited me. > > Some words about myself: I have experience

Re: Setting existing property from single value to multi-value

great. Regards Julian On Wed, Jul 24, 2019 at 6:52 AM Julian Reschke wrote: > > On 24.07.2019 05:55, Julian Reschke wrote: > > On 23.07.2019 23:57, Julian Sedding wrote: > >> Hi all > >> > >> Let's assume we have a Node N of primary type "nt:unstruct

Setting existing property from single value to multi-value

Hi all Let's assume we have a Node N of primary type "nt:unstructured" with property P that has a String value "foo". Now when we try to change the value of P to a String[] value of ["foo", "bar"] a ValueException is thrown. This behaviour was introduced in OAK-273. Unfortunately the ticket

Re: svn commit: r1834852 - /jackrabbit/oak/trunk/oak-segment-tar/src/test/java/org/apache/jackrabbit/oak/segment/osgi/

Hi Francesco Have you considered using the MetaTypeReader from Felix' MetyType implementation[0]? I've used it before and found it easy enough to use. It's only a test dependency, and you don't need to worry about your implementation being in sync with the spec/Felix' implementation. Regards

Re: Looking for small task starting in OAK .. DS conversion?

gt; is bug free. > > Christian > > 2017-10-30 13:40 GMT+01:00 Julian Sedding <jsedd...@gmail.com>: > >> Hi Christian >> >> I have worked on OAK-6741 before and there were some concerns >> regarding my changes. >> >> To address these concerns, I

Re: Looking for small task starting in OAK .. DS conversion?

Hi Christian I have worked on OAK-6741 before and there were some concerns regarding my changes. To address these concerns, I started work on a tool that allows diffing the OSGi DS and MetaType metadata of two bundles. It uses Felix' SCR and MetaType implementations to parse the metadata and

Re: Naming convention for unstable releases

+1 for any qualifier indicating "unstable" releases. Regards Julian On Tue, Oct 17, 2017 at 7:28 AM, Julian Reschke wrote: > Hi there, > > everybody over here knows that odd-numbered releases are unstable, taken > from trunk. > > However, apparently not all of our users

Re: clustering and cold standby

Hi Marco Cold Standby is a TarMK feature that allows for a quick failover. You may think of it as a near real-time backup. It is _not_ a cluster. As you noted, the sync is one-way only. Therefore, I don't think it is possible to direct reads or writes to the cold standby instance. AFAIK this

Dependency to DropWizard Metrics Library (was: Percentile implementation)

djustments and will revisit the percentile >> implementation once we'll change our use pattern there. >> >> Regards, >> Andrei >> >> 2017-07-06 14:38 GMT+03:00 Chetan Mehrotra <chetan.mehro...@gmail.com>: >> >>> Instead of commons-math can w

Re: [DiSCUSS] - highly vs rarely used data

>From my experience working with customers, I can pretty much guarantee that sooner or later: (a) the implementation of an automatism is not *quite* what they need/want (b) they want to be able to manually select (or more likely override) whether a file can be archived Thus I suggest to come up

Re: copy on write node store

Slightly off topic: the thought that the copy on read/write indexing features may need to be explicitly managed in such a setup just occurred to me. I.e. when an instance is switched to the copy on write node store, the local index directory will deviate from the "mainline" node store. Upon

Re: New Jackrabbit Committer: Robert Munteanu

Welcome Robert! Keep up the good work! Regards Julian On Tue, May 23, 2017 at 1:08 PM, Robert Munteanu wrote: > Hi, > > On Mon, 2017-05-22 at 13:53 +0200, Michael Dürig wrote: >> Hi, >> >> Please welcome Robert as a new committer and PMC member of the >> Apache >> Jackrabbit

Re: upgrade repository structure with backward-incompatible changes

com> wrote: > Hi Julian, > I meant I'm using Oak not Sing. Yes I'm using JCR API. > > Marco. > > On Fri, May 19, 2017 at 2:22 PM, Julian Sedding <jsedd...@gmail.com> wrote: > >> Hi Marco >> >> On Fri, May 19, 2017 at 2:10 PM, Marco Piovesana <pioves...@es

Re: upgrade repository structure with backward-incompatible changes

arco. > > On Fri, May 19, 2017 at 10:39 AM, Julian Sedding <jsedd...@gmail.com> wrote: > >> Hi Marco >> >> It sounds like you are dealing with a JCR-based application and thus >> you should be using the JCR API (directly or indirectly, e.g. via >> Sling

Re: upgrade repository structure with backward-incompatible changes

Hi Marco It sounds like you are dealing with a JCR-based application and thus you should be using the JCR API (directly or indirectly, e.g. via Sling) to change your content. CommitHook is an Oak internal API that does not enforce any JCR semantics. So if you were to go down that route, you

Re: new name for the multiplexing node store

+1 to CompositeNodeStore Regards Julian On Thu, May 11, 2017 at 10:36 AM, Bertrand Delacretaz wrote: > On Thu, May 11, 2017 at 9:33 AM, Robert Munteanu wrote: >> ...MultiplexingNodeStore is a pretty standard implementation >> of the Composite design

Re: new name for the multiplexing node store

Hi Tomek In all related discussions the term "mount" appears a lot. So why not Mounting NodeStore? The module could be "oak-store-mount". Regards Julian On Fri, May 5, 2017 at 1:39 PM, Tomek Rekawek wrote: > Hello oak-dev, > > the multiplexing node store has been recently

Re: oak-run: Enforcing size

I also think that the build should not produce different artifacts depending on a profile. If the jar file gets too big when embedding the JDBC driver, we may want to consider producing two build artifacts: the jar file without RDB support and another one (e.g. with classifier "rdb") that embeds

Re: [ops] Unify NodeStore/DataStore configurations by using nstab

Hi Arek I agree that we could benefit from a way to bootstrap a repository from a single configuration file. Regarding the format you suggest, I am sceptical that it is suitable to cover all (required) complexities of setting up a repository. Consider that besides the persistence, there are

Re: [m12n] Location of InitialContent

Hi Angela >From the features you describe it sounds like it should go into org.apache.jackrabbit.oak.jcr (or at least most of it). It looks like it is being used in lots of tests in oak-core, however, so this may just be wishful thinking... Regards Julian On Thu, Apr 20, 2017 at 10:07 AM,

Re: [DISCUSS] Which I/O statistics should the FileStore expose?

Hi Francesco I believe you should implement an IOMonitor using the metrics in the org.apache.jackrabbit.oak.stats package. These can be backed by swappable StatisticsProvider implementations. I believe by default it's a NOOP implementation. However, I believe that if the MetricStatisticsProvider

Re: Slowness while multiple uploads

If I read the code correctly, you only logout the session in a catch block. Assuming the code is otherwise sane, that would indicate a session leak, because most sessions are not logged out. That could also explain the gradual slowdown over two days. You have to always logout JCR sessions that

Re: New Jackrabbit Committer: Andrei Dulceanu

Congratulations Andrei & welcome to the team! Regards Julian On Mon, Dec 19, 2016 at 9:35 AM, Michael Dürig wrote: > Hi, > > Please welcome Andrei as a new committer and PMC member of the Apache > Jackrabbit project. The Jackrabbit PMC recently decided to offer Andrei >

Clarifiing Blob#getReference and BlobStore#getReference

Hi all I was wondering if Blob#getReference could be used in AbstractBlob#equal to optimize blob comparison (OAK-5253). Specifically whether blobA.getReference() != blobB.getReference() (pseudocode) allows us to determine that the blobs are not equal. However, the API docs[0,1] only state that

Re: Is Lucene CopyOnRead/CopyOnWrite beneficial with SegmentNodeStore?

rectory support providing better performance. > > Some old numbers can be seen at [1] > > Chetan Mehrotra > [1] > https://issues.apache.org/jira/browse/OAK-1702?focusedCommentId=13965551=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13965551 > > &g

Is Lucene CopyOnRead/CopyOnWrite beneficial with SegmentNodeStore?

Hi all Do we have experience or measurements to suggest that using Lucene's CopyOnRead and CopyOnWrite features is beneficial when the SegmentNodeStore isused? The documentation indirectly suggests that CopyOnRead is only beneficial with remote NodeStores (i.e. DocumentNodeStore). So the

Re: [VOTE] Release Apache Jackrabbit Oak 1.4.10

+1 Release this package as Apache Jackrabbit Oak 1.4.10 Regards Julian On Fri, Nov 11, 2016 at 6:38 AM, Amit Jain wrote: > On Thu, Nov 10, 2016 at 7:23 PM, Davide Giannella wrote: > >> Please vote on releasing this package as Apache Jackrabbit Oak 1.4.10. >>

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.13

+1 Release this package as Apache Jackrabbit Oak 1.5.13 Regards Julian On Wed, Nov 9, 2016 at 10:29 AM, Alex Parvulescu wrote: > [X] +1 Release this package as Apache Jackrabbit Oak 1.5.13 > > On Tue, Nov 8, 2016 at 4:33 PM, Davide Giannella wrote:

Re: svn commit: r1767830 - in /jackrabbit/oak/trunk/oak-upgrade/src: main/java/org/apache/jackrabbit/oak/upgrade/security/AuthorizableFolderEditor.java test/java/org/apache/jackrabbit/oak/upgrade/Auth

Sorry, my bad. Thanks Chetan! On Thu, Nov 3, 2016 at 8:58 AM, wrote: > Author: chetanm > Date: Thu Nov 3 07:58:35 2016 > New Revision: 1767830 > > URL: http://svn.apache.org/viewvc?rev=1767830=rev > Log: > OAK-5043: Very old JR2 repositories may have invalid nodetypes for

[jira] [Commented] (JCRVLT-138) Unzip test-packages for easier maintenance

[ https://issues.apache.org/jira/browse/JCRVLT-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621925#comment-15621925 ] Julian Sedding commented on JCRVLT-138: --- Thanks for the quick fix! Looks good to me and should make

Re: svn commit: r1767213 [1/4] - in /jackrabbit/commons/filevault/trunk: parent/ vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/impl/ vault-core/src/test/java/org/apache/jackrabbit/vau

Hi Tobi Thanks for the change. Note: some of the files from the extracted packages have Adobe headers and other are missing the Apache license headers. Regards Julian On Mon, Oct 31, 2016 at 2:55 AM, wrote: > Author: tripod > Date: Mon Oct 31 01:55:37 2016 > New Revision:

Re: segment-tar depending on oak-core

Hi all My preference is also with a higher degree of modularity. Compared to a monolithic application it is a trade-off that leads to both, higher complexity and higher flexibility. Provided we are willing to change and learn, I am sure we can easily manage the complexity. Numerous benefits of

[jira] [Comment Edited] (JCRVLT-111) Add support for o.a.j.api.security.authorization.PrincipalSetPolicy

[ https://issues.apache.org/jira/browse/JCRVLT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15617748#comment-15617748 ] Julian Sedding edited comment on JCRVLT-111 at 10/29/16 8:56 AM: - [~tripod

[jira] [Created] (JCRVLT-138) Unzip test-packages for easier maintenance

Julian Sedding created JCRVLT-138: - Summary: Unzip test-packages for easier maintenance Key: JCRVLT-138 URL: https://issues.apache.org/jira/browse/JCRVLT-138 Project: Jackrabbit FileVault

[jira] [Commented] (JCRVLT-111) Add support for o.a.j.api.security.authorization.PrincipalSetPolicy

[ https://issues.apache.org/jira/browse/JCRVLT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15617748#comment-15617748 ] Julian Sedding commented on JCRVLT-111: --- [~tripod] if you look at the implementation

Re: svn commit: r1765583 - in /jackrabbit/oak/trunk: oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/ oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ oak-cor

Thanks Chetan! On Fri, Oct 21, 2016 at 2:59 PM, Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: > On Thu, Oct 20, 2016 at 6:08 PM, Julian Sedding <jsedd...@gmail.com> wrote: >> I think we could get away with increasing this to 4.1.0 if we can >> annota

Re: segment-tar depending on oak-core

> All of this is my understanding and I may be wrong, so please correct me > if I'm wrong. I'm right, could adding an oak-core-api with independent > lifecycle solve the situation? While this may be possible, an arguably simpler solution would be to give oak-run and oak-upgrade a separate

Re: [REVIEW] Configuration required for node bundling config for DocumentNodeStore - OAK-1312

+1 for initializing the default config unconditionally Regards Julian On Fri, Oct 21, 2016 at 12:14 PM, Chetan Mehrotra wrote: > Opened OAK-4975 for query around default config handling. > Chetan Mehrotra > > > On Fri, Oct 21, 2016 at 2:14 PM, Davide Giannella

Re: svn commit: r1765583 - in /jackrabbit/oak/trunk: oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/ oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ oak-cor

> -@Version("4.0.0") > +@Version("5.0.0") > @Export(optional = "provide:=true") > package org.apache.jackrabbit.oak.api.jmx; I think we could get away with increasing this to 4.1.0 if we can annotate QueryEngineSettingsMBean with @ProviderType. I.e. we don't expect API consumers to implement

Re: Possibility of making nt:resource unreferenceable

On Wed, Oct 12, 2016 at 11:24 AM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > On Wed, Oct 12, 2016 at 11:18 AM, Julian Sedding <jsedd...@gmail.com> wrote: >> ...As a remedy for implementations that rely on the current referencable >> nature, we could provide

Re: Possibility of making nt:resource unreferenceable

I'm with Julian R. on this (as I understand him). We should change the node-type nt:resource to match the JCR 2.0 spec and deal with the consequences. Currently I am under the impression that we have no knowledge of what *might* break, with varying opinions on the matter. Maybe we should to find

Re: Datastore GC only possible after Tar Compaction

but possibly many false negatives. Regards Julian On Mon, Oct 3, 2016 at 10:37 AM, Amit Jain <am...@ieee.org> wrote: > Hi, > > On Mon, Oct 3, 2016 at 1:29 PM, Julian Sedding <jsedd...@apache.org> wrote: > >> I just became aware that on a system configured with Segment

Datastore GC only possible after Tar Compaction

Hi all I just became aware that on a system configured with SegmentNodeStore and FileDatastore a Datastore garbage collection can only free up space *after* a Tar Compaction was run. This behaviour is not immediately intuitive to me. I would like to discuss whether it is desirable to require a

Re: [VOTE] Require JDK7 for Oak 1.4

+1 Regards Julian On Mon, Sep 19, 2016 at 11:22 AM, Michael Dürig wrote: > > > On 16.9.16 5:16 , Julian Reschke wrote: >> >> [X] +1 Yes, require JDK7 for Oak 1.4 > > > Michael

Re: Requirement to support multiple NodeStore instance in same setup (OAK-4490)

Hi Chetan I agree that we should not rely on the service.ranking for this. A type property makes sense IMO. On the other hand, do we really need to expose both NodeStores in the service registry? The secondary (cache) NodeStore could also be treated as an implementation detail of the

Re: [VOTE] Release Apache Jackrabbit 2.10.3

[X] +1 Release this package as Apache Jackrabbit 2.10.3 Regards Julian On Mon, May 9, 2016 at 10:06 AM, Amit Jain wrote: > A candidate for the Jackrabbit 2.10.3 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/2.10.3/ > > The release candidate

Re: Duplicate logic in oak-run commands

Hi Francesco +1 for centralizing logic for creating a NodeStore instance. I like the idea of encoding the description of a NodeStore instance in a URI. This is both concise and extensible. We need to also consider how to express the use of different DataStores as well. I.e. the URI should

[jira] [Commented] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[ https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262151#comment-15262151 ] Julian Sedding commented on JCR-3971: - The following system property is supported: {noformat

[jira] [Commented] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[ https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262148#comment-15262148 ] Julian Sedding commented on JCR-3972: - The following two system properties are supported: {noformat

Re: [VOTE] Please vote for the final name of oak-segment-next

Hi +1 for oak-segment-file or oak-segment-tar. +0 for oak-segment-store. We *may* implement another segment-based persistence later, in which case having the persistence strategy in the name sounds like a good idea to me. Similarly, a later refactoring of the document store could lead to

[jira] [Updated] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[ https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated JCR-3971: Fix Version/s: 2.10.3 2.8.2 > Make read-permission cache-s

[jira] [Resolved] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[ https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved JCR-3971. - Resolution: Fixed > Make read-permission cache-size in CompiledPermissionsImpl configura

[jira] [Resolved] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[ https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved JCR-3972. - Resolution: Fixed > Make size of ID-cache in CachingHierarchyManager configura

[jira] [Comment Edited] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[ https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256235#comment-15256235 ] Julian Sedding edited comment on JCR-3971 at 4/25/16 12:23 PM: --- Fixed in trunk

[jira] [Updated] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[ https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated JCR-3972: Fix Version/s: 2.10.3 2.8.2 > Make size of ID-cache in CachingHierarchyMana

[jira] [Comment Edited] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[ https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256236#comment-15256236 ] Julian Sedding edited comment on JCR-3972 at 4/25/16 12:23 PM: --- Fixed in trunk

[jira] [Updated] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[ https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated JCR-3971: Fix Version/s: 2.12.2 > Make read-permission cache-size in CompiledPermissionsImpl configura

[jira] [Updated] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[ https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated JCR-3971: Affects Version/s: 2.8.1 2.10.2 > Make read-permission cache-s

[jira] [Updated] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[ https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated JCR-3972: Fix Version/s: 2.12.2 > Make size of ID-cache in CachingHierarchyManager configura

[jira] [Updated] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[ https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated JCR-3972: Affects Version/s: 2.8.1 2.10.2 > Make size of ID-ca

[jira] [Commented] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[ https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256235#comment-15256235 ] Julian Sedding commented on JCR-3971: - Fixed in trunk [r1740814|https://svn.apach.org/r1740814

[jira] [Commented] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[ https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256236#comment-15256236 ] Julian Sedding commented on JCR-3972: - Fixed in trunk [r1740815|https://svn.apach.org/r1740815

[jira] [Created] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

Julian Sedding created JCR-3972: --- Summary: Make size of ID-cache in CachingHierarchyManager configurable Key: JCR-3972 URL: https://issues.apache.org/jira/browse/JCR-3972 Project: Jackrabbit Content

[jira] [Created] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

Julian Sedding created JCR-3971: --- Summary: Make read-permission cache-size in CompiledPermissionsImpl configurable Key: JCR-3971 URL: https://issues.apache.org/jira/browse/JCR-3971 Project: Jackrabbit

Re: Cannot create JIRA issue for JCR project

24 PM Robert Munteanu <romb...@apache.org> wrote: >> >> On Fri, 2016-04-22 at 15:27 +0200, Julian Sedding wrote: >> > Hi all >> > >> > I can currently not log a JIRA issue for the JCR project. It is not >> > listed in the Create dialog's project dropdown. Oth

Cannot create JIRA issue for JCR project

Hi all I can currently not log a JIRA issue for the JCR project. It is not listed in the Create dialog's project dropdown. Other projects, e.g. Jackrabbit Oak, Sling etc. are listed. Any ideas? Could it be related to the recent infra changes on JIRA? Should I contact infra? Thanks Julian

Re: Deprecation of 2.2.x plan

+1 Regards Julian On Wed, Apr 20, 2016 at 7:01 AM, KÖLL Claus wrote: > +1 > > greets > claus > > -Ursprüngliche Nachricht- > Von: Davide Giannella [mailto:dav...@apache.org] > Gesendet: Dienstag, 19. April 2016 15:57 > An: dev > Betreff: Deprecation of 2.2.x plan >

Re: Increase language level to Java 7

We could enforce java6 signatures for the branches using the animal-sniffer-maven-plugin. This should help detect bogus backports quickly. Regards Julian On Thu, Apr 7, 2016 at 10:57 AM, Francesco Mari wrote: > Language features would be available for new,

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.0

[X] +1 Release this package as Apache Jackrabbit Oak 1.5.0 Regards Julian On Tue, Mar 29, 2016 at 3:07 PM, Alex Parvulescu wrote: > [X] +1 Release this package as Apache Jackrabbit Oak 1.5.0 > > best, > alex > > On Tue, Mar 29, 2016 at 10:57 AM, Amit Jain

Re: [VOTE] Release Apache Jackrabbit Oak 1.4.1

[X] +1 Release this package as Apache Jackrabbit Oak 1.4.1 Regards Julian On Wed, Mar 30, 2016 at 1:52 PM, Julian Reschke wrote: > On 2016-03-24 15:32, Davide Giannella wrote: >> >> ... > > > [X] +1 Release this package as Apache Jackrabbit Oak 1.4.1 > > Best regards,

Re: New Jackrabbit committer: Tomek Rękawek

Congratulations Tomek! Regards Julian On Tue, Mar 22, 2016 at 12:05 PM, Manfred Baedke wrote: > Welcome, Tomek! > > Manfred > > > On 3/21/2016 6:21 PM, Michael Dürig wrote: >> >> Hi, >> >> Please welcome Tomek as a new committer and PMC member of the Apache >>

Re: [VOTE] Release Apache Jackrabbit Oak 1.4.0 (take 3)

[X] +1 Release this package as Apache Jackrabbit Oak 1.4.0 Regards Julian On Mon, Mar 7, 2016 at 11:51 AM, Davide Giannella wrote: > A candidate for the Jackrabbit Oak 1.4.0 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.4.0/ > > The

Re: svn commit: r1733315 - /jackrabbit/oak/branches/1.4/RELEASE-NOTES.txt

Nitpick: > +Changes in Oak 1.2.0 IMHO that should be "Changes in Oak 1.4.0" This probably doesn't warrant a re-release, but if there *is* a re-release due to OAK-4085[0] it would be nice to correct it. Regards Julian [0] https://issues.apache.org/jira/browse/OAK-4085 On Wed, Mar 2, 2016 at

Re: testing blob equality

Yes, the LengthCachingDataStore is exactly the way to go. You need to wrap the original datastore in the length caching datastore (using the repository.xml). The LengthCachingDataStore not only caches the length, but (for the FileDataStore at least) it also prevents a call to File.exists(). These

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

The test failures in the issue seem to suggest that this may be relates to simple versionables. IIRC we recently added support for some broken JR2 constructs. Could they have been fixed in the last JR release? If that's the case it may no longer be possible to populate the source repository for

Re: Anchor tags on doc pages get positioned wrongly under top menu

Hi Vikas I agree that having the anchor text hidden is a usability hazard. I tried your suggested approach in Firefox (via FireBug) and didn't have any success. However, a slight variation of the scheme, still relying on the ":target" pseudo selector, did the trick for me. h2 > a:target {

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.15

[X] +1 Release this package as Apache Jackrabbit Oak 1.3.15 Regards Julian On Wed, Feb 3, 2016 at 10:44 PM, Alex Parvulescu wrote: > [X] +1 Release this package as Apache Jackrabbit Oak 1.3.15 > > On Wed, Feb 3, 2016 at 5:00 PM, Davide Giannella

Re: svn commit: r1727297 - /jackrabbit/oak/trunk/oak-run/src/main/java/org/apache/jackrabbit/oak/run/Main.java

file); > > > On Fri, Jan 29, 2016 at 5:41 PM, Julian Sedding <jsedd...@gmail.com> wrote: > >> > + System.out.println("Debug " + file); >> >> Is this on purpose or an oversight? >> >> Regards >> Julian >> >> On Thu, Jan 28, 201

Re: svn commit: r1727297 - /jackrabbit/oak/trunk/oak-run/src/main/java/org/apache/jackrabbit/oak/run/Main.java

> + System.out.println("Debug " + file); Is this on purpose or an oversight? Regards Julian On Thu, Jan 28, 2016 at 10:56 AM, wrote: > Author: alexparvulescu > Date: Thu Jan 28 09:56:31 2016 > New Revision: 1727297 > > URL:

[jira] [Commented] (JCR-3937) jackrabbit-jcr-commons bundle incorrectly has google dependency in Export-Package uses clause

[ https://issues.apache.org/jira/browse/JCR-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15055990#comment-15055990 ] Julian Sedding commented on JCR-3937: - I suggest to update to maven-bundle-plugin version 3.0.1 due

Re: fixVersions in jira

+1 - Setting the next release as fixVersion for blockers makes sense. For all other issues setting the fixVersion once it is fixed seems more sensible. Regards Julian On Tue, Dec 8, 2015 at 8:27 AM, Marcel Reutegger wrote: > On 07/12/15 14:55, "Davide Giannella" wrote: >>The

Re: Segment Store modularization

I agree with Francesco. SNFE should be an implementation detail of the Segment bundle. If any code outside of this module depends on SNFE in order to handle it differently, I would consider that a leaked abstraction. The special handling should instead be moved into the Segment bundle (which may

  1   2   >