On 2017-07-03 15:52, Davide Giannella wrote:
...
[X] +1 Release this package as Apache Jackrabbit Oak 1.7.3
Best regards, Julian
+1
Tommaso
Il giorno lun 3 lug 2017 alle ore 17:20 Alex Deparvu
ha scritto:
> +1
>
> On Mon, Jul 3, 2017 at 3:52 PM, Davide Giannella
> wrote:
> > A candidate for the Jackrabbit Oak 1.7.3 release is available at:
> >
> >
+1
On Mon, Jul 3, 2017 at 3:52 PM, Davide Giannella wrote:
> A candidate for the Jackrabbit Oak 1.7.3 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.3/
>
> The release candidate is a zip archive of the sources in:
>
>
>
Hi Andrei,
Ok, here is the context, apologize for not starting with that first.
I’m working on a PTR (point in time restore) proof of concept involving large
asset repositories. The easy way for small-ish repos would be to backup
everyday everything and when the customer pops by and says “I
[X] +1 Release this package as Apache Jackrabbit Oak 1.7.3
Davide
I am sure there are both use cases for automatic vs manual/controlled
collection of unused data, however if I were a user I would personally not
want to care about this. While I'd be happy to know that my repo is faster
/ smaller / cleaner / whatever it'd sound overly complex to deal with JCR
and
A candidate for the Jackrabbit Oak 1.7.3 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.3/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.3/
The SHA1 checksum of the
Hi Andrei,
AFAIK, there isn't currently such an option for the consistency check. What
scenario do you have in mind for using it?
Regards,
Andrei
2017-07-03 16:32 GMT+03:00 Andrei Kalfas :
> Hi,
>
> I’m reading about the consistency check tool thats available via
Hi,
> a property on the node, e.g. "archiveState=toArchive"
I wonder if we _can_ easily write to the version store? Also, some nodetypes
don't allow such properties? It might need to be a hidden property, but then
you can't use the JCR API. Or maintain this data in a "shadow" structure (not
+1
On Mon, Jul 3, 2017 at 11:51 AM, Marcel Reutegger
wrote:
> Hi,
>
> I'd like to backport OAK-6410 to the maintenance branches. It fixes a NPE
> when an attempt is made to remove an inexistent property from a checked in
> node. I consider this a low risk fix.
>
>
On 2017-07-03 11:51, Marcel Reutegger wrote:
Hi,
I'd like to backport OAK-6410 to the maintenance branches. It fixes a NPE when
an attempt is made to remove an inexistent property from a checked in node. I
consider this a low risk fix.
Regards
Marcel
+1
Hi,
I'd like to backport OAK-6410 to the maintenance branches. It fixes a NPE when
an attempt is made to remove an inexistent property from a checked in node. I
consider this a low risk fix.
Regards
Marcel
The Apache Jenkins build system has built Jackrabbit Oak (build #488)
Status: Failure
Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/488/ to
view the results.
Changes:
[chetanm] Update docs related to indexPath support
[chetanm] OAK-6271 - Support for importing index
13 matches
Mail list logo