[jira] [Commented] (JCR-3661) jcrvlt: String[]{""} not packaged correctly
[
https://issues.apache.org/jira/browse/JCR-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762126#comment-13762126
]
Tobias Bocanegra commented on JCR-3661:
---
currently the versions are the one from jackrabbit. we have to wait until
infra created the new jira project for vlt. then we can move the issues and
use the correct versions.
> jcrvlt: String[]{""} not packaged correctly
> ---
>
> Key: JCR-3661
> URL: https://issues.apache.org/jira/browse/JCR-3661
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
>
> A MV property with 1 empty string value is serialized as "[]". When
> deserialized, this results in an empty MV property with 0 values.
> eg:
>
> http://sling.apache.org/jcr/sling/1.0";
> xmlns:jcr="http://www.jcp.org/jcr/1.0";
> jcr:primaryType="sling:Folder"
> allowedChildren="[]"/>
> This is a flaw in the DocViewPropertyFormat. the simplest solution is to mark
> an empty string value with \0.
> eg:
> allowedChildren="[\0]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3651) S3 Datastore implementation
[ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3651: Attachment: JCR-3651-svn-updated.patch > S3 Datastore implementation > --- > > Key: JCR-3651 > URL: https://issues.apache.org/jira/browse/JCR-3651 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-core >Affects Versions: 2.7 >Reporter: Shashank Gupta > Fix For: 2.7.1 > > Attachments: JCR-3651.patch, JCR-3651-svn.patch, > JCR-3651-svn-updated.patch > > > S3 Datastore provides capability to use Amazon S3 as datastore, thus > leveraging all benefits of Amazon S3 like low cost, infinite, reliable, > scalable storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3651) S3 Datastore implementation
[ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3651: Attachment: (was: JCR-3651-svn-updated.patch) > S3 Datastore implementation > --- > > Key: JCR-3651 > URL: https://issues.apache.org/jira/browse/JCR-3651 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-core >Affects Versions: 2.7 >Reporter: Shashank Gupta > Fix For: 2.7.1 > > Attachments: JCR-3651.patch, JCR-3651-svn.patch, > JCR-3651-svn-updated.patch > > > S3 Datastore provides capability to use Amazon S3 as datastore, thus > leveraging all benefits of Amazon S3 like low cost, infinite, reliable, > scalable storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3651) S3 Datastore implementation
[ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3651: Attachment: JCR-3651-svn.patch [~tmueller] thanks for the feedback. have incorporated all comments. > S3 Datastore implementation > --- > > Key: JCR-3651 > URL: https://issues.apache.org/jira/browse/JCR-3651 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-core >Affects Versions: 2.7 >Reporter: Shashank Gupta > Fix For: 2.7.1 > > Attachments: JCR-3651.patch, JCR-3651-svn.patch, > JCR-3651-svn-updated.patch > > > S3 Datastore provides capability to use Amazon S3 as datastore, thus > leveraging all benefits of Amazon S3 like low cost, infinite, reliable, > scalable storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3651) S3 Datastore implementation
[ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3651: Attachment: JCR-3651-svn-updated.patch > S3 Datastore implementation > --- > > Key: JCR-3651 > URL: https://issues.apache.org/jira/browse/JCR-3651 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-core >Affects Versions: 2.7 >Reporter: Shashank Gupta > Fix For: 2.7.1 > > Attachments: JCR-3651.patch, JCR-3651-svn.patch, > JCR-3651-svn-updated.patch > > > S3 Datastore provides capability to use Amazon S3 as datastore, thus > leveraging all benefits of Amazon S3 like low cost, infinite, reliable, > scalable storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3651) S3 Datastore implementation
[ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3651: Attachment: (was: JCR-3651-svn.patch) > S3 Datastore implementation > --- > > Key: JCR-3651 > URL: https://issues.apache.org/jira/browse/JCR-3651 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-core >Affects Versions: 2.7 >Reporter: Shashank Gupta > Fix For: 2.7.1 > > Attachments: JCR-3651.patch, JCR-3651-svn.patch, > JCR-3651-svn-updated.patch > > > S3 Datastore provides capability to use Amazon S3 as datastore, thus > leveraging all benefits of Amazon S3 like low cost, infinite, reliable, > scalable storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: September Board Report
On 9.9.13 12:01 , Marcel Reutegger wrote: just one minor correction: the 2.6.3 release was done from the 2.6 branch and not from trunk. Thanks for spotting, fixed. Michael
RE: September Board Report
Hi, just one minor correction: the 2.6.3 release was done from the 2.6 branch and not from trunk. regards marcel > -Original Message- > From: Michael Dürig [mailto:mdue...@apache.org] > Sent: Montag, 9. September 2013 10:46 > To: dev@jackrabbit.apache.org > Subject: September Board Report > > > Hi, > > I've assembled a preliminary board report for September: > > https://wiki.apache.org/jackrabbit/Board%20Report%20September%202013 > > Let me know if there is anything missing or broken in the report. I plan > to submit it tomorrow evening CET. > > > Michael
[jira] [Commented] (JCR-3652) Bundle serialization broken
[ https://issues.apache.org/jira/browse/JCR-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761727#comment-13761727 ] Jan Haderka commented on JCR-3652: -- [~tmueller] Is this issue affecting only 2.4 and 2.7 branches but working fine on 2.6? Thx. > Bundle serialization broken > --- > > Key: JCR-3652 > URL: https://issues.apache.org/jira/browse/JCR-3652 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-core >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Minor > Fix For: 2.4.4, 2.7.1 > > Attachments: JCR-3652-b.patch, JCR-3652.patch, > JCR-3652-test-case.patch > > > I have got a strange case where some node bundle is broken, seemingly because > a byte is missing. I can't explain the missing byte, but it is reproducible, > meaning that writing the bundles again will break them again. There are 11 > broken bundles, 10 of them have the size 480 bytes and one is slightly > larger. It is always a boolean property value that is missing, always the > value for the property jcr:isCheckedOut. > As a (temporary) solution, and to help analyze what the problem might be, I > will create a patch that does the following: > * When serializing a bundle, check if the byte array can be de-serialized. If > not, then try again. Starting with the 3th try, use a slower variant where > before and after writing the boolean value the buffer is flushed. I'm aware > that ByteArrayOutputStream.flush doesn't do much, but maybe it solves the > problem (let's see) if the problem is related to a JVM issue. > * If de-serializing a bundle fails, check if it's because of a missing > boolean property value. If yes, insert the missing byte. > I have also added some log messages (warning / error) to help analyze the > problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3661) jcrvlt: String[]{""} not packaged correctly
[
https://issues.apache.org/jira/browse/JCR-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761724#comment-13761724
]
Jan Haderka commented on JCR-3661:
--
[~tripod] Can you set the fix version on this issue? Is it going out only w/
3.0?
> jcrvlt: String[]{""} not packaged correctly
> ---
>
> Key: JCR-3661
> URL: https://issues.apache.org/jira/browse/JCR-3661
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
>
> A MV property with 1 empty string value is serialized as "[]". When
> deserialized, this results in an empty MV property with 0 values.
> eg:
>
> http://sling.apache.org/jcr/sling/1.0";
> xmlns:jcr="http://www.jcp.org/jcr/1.0";
> jcr:primaryType="sling:Folder"
> allowedChildren="[]"/>
> This is a flaw in the DocViewPropertyFormat. the simplest solution is to mark
> an empty string value with \0.
> eg:
> allowedChildren="[\0]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3665) Loading nodes in index and database consistency checkers might fail when the last node of a batch was removed concurrently
[ https://issues.apache.org/jira/browse/JCR-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3665: -- Fix Version/s: 2.7.1 2.6.4 > Loading nodes in index and database consistency checkers might fail when the > last node of a batch was removed concurrently > -- > > Key: JCR-3665 > URL: https://issues.apache.org/jira/browse/JCR-3665 > Project: Jackrabbit Content Repository > Issue Type: Bug >Reporter: Unico Hommes >Assignee: Unico Hommes > Fix For: 2.6.4, 2.7.1 > > > In both the index and database consistency checkers, when nodes are loaded in > batches from the database, the next batch may unexpectedly fail to load when > the last node of the previous batch was removed in the mean time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3665) Loading nodes in index and database consistency checkers might fail when the last node of a batch was removed concurrently
[ https://issues.apache.org/jira/browse/JCR-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3665: -- Description: In both the index and database consistency checkers, when nodes are loaded in batches from the database, the next batch may unexpectedly fail to load when the last node of the previous batch was removed in the mean time. (was: In both the index and database consistency checkers, when nodes are loaded in batches from the database, the next batch may unexpectedly fail to load because the last node of the previous batch was removed in the mean time.) > Loading nodes in index and database consistency checkers might fail when the > last node of a batch was removed concurrently > -- > > Key: JCR-3665 > URL: https://issues.apache.org/jira/browse/JCR-3665 > Project: Jackrabbit Content Repository > Issue Type: Bug >Reporter: Unico Hommes >Assignee: Unico Hommes > > In both the index and database consistency checkers, when nodes are loaded in > batches from the database, the next batch may unexpectedly fail to load when > the last node of the previous batch was removed in the mean time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (JCR-3665) Loading nodes in index and database consistency checkers might fail when the last node of a batch removed concurrently
Unico Hommes created JCR-3665: - Summary: Loading nodes in index and database consistency checkers might fail when the last node of a batch removed concurrently Key: JCR-3665 URL: https://issues.apache.org/jira/browse/JCR-3665 Project: Jackrabbit Content Repository Issue Type: Bug Reporter: Unico Hommes Assignee: Unico Hommes In both the index and database consistency checkers, when nodes are loaded in batches from the database, the next batch may unexpectedly fail to load because the last node of the previous batch was removed in the mean time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3665) Loading nodes in index and database consistency checkers might fail when the last node of a batch was removed concurrently
[ https://issues.apache.org/jira/browse/JCR-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3665: -- Summary: Loading nodes in index and database consistency checkers might fail when the last node of a batch was removed concurrently (was: Loading nodes in index and database consistency checkers might fail when the last node of a batch removed concurrently) > Loading nodes in index and database consistency checkers might fail when the > last node of a batch was removed concurrently > -- > > Key: JCR-3665 > URL: https://issues.apache.org/jira/browse/JCR-3665 > Project: Jackrabbit Content Repository > Issue Type: Bug >Reporter: Unico Hommes >Assignee: Unico Hommes > > In both the index and database consistency checkers, when nodes are loaded in > batches from the database, the next batch may unexpectedly fail to load > because the last node of the previous batch was removed in the mean time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
September Board Report
Hi, I've assembled a preliminary board report for September: https://wiki.apache.org/jackrabbit/Board%20Report%20September%202013 Let me know if there is anything missing or broken in the report. I plan to submit it tomorrow evening CET. Michael
