[jira] [Created] (JCR-3754) [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload
Shashank Gupta created JCR-3754: --- Summary: [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload Key: JCR-3754 URL: https://issues.apache.org/jira/browse/JCR-3754 Project: Jackrabbit Content Repository Issue Type: Improvement Reporter: Shashank Gupta Currently s3 asynchronous uploads are not retried after failure. since failed upload file is served from local cache it doesn't hamper datastore functionality. During next restart all accumulated failed upload files are uploaded to s3 in synchronized manner. There should be retry logic for failed s3 asynchronous upload so that failed uploads are not accumulated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JCR-3754) [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload
[ https://issues.apache.org/jira/browse/JCR-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3754: Component/s: jackrabbit-data Affects Version/s: 2.7.5 Fix Version/s: 2.7.6 [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload - Key: JCR-3754 URL: https://issues.apache.org/jira/browse/JCR-3754 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-data Affects Versions: 2.7.5 Reporter: Shashank Gupta Fix For: 2.7.6 Currently s3 asynchronous uploads are not retried after failure. since failed upload file is served from local cache it doesn't hamper datastore functionality. During next restart all accumulated failed upload files are uploaded to s3 in synchronized manner. There should be retry logic for failed s3 asynchronous upload so that failed uploads are not accumulated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JCR-3754) [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload
[ https://issues.apache.org/jira/browse/JCR-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3754: Attachment: JCR-3754.patch [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload - Key: JCR-3754 URL: https://issues.apache.org/jira/browse/JCR-3754 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-data Affects Versions: 2.7.5 Reporter: Shashank Gupta Fix For: 2.7.6 Attachments: JCR-3754.patch Currently s3 asynchronous uploads are not retried after failure. since failed upload file is served from local cache it doesn't hamper datastore functionality. During next restart all accumulated failed upload files are uploaded to s3 in synchronized manner. There should be retry logic for failed s3 asynchronous upload so that failed uploads are not accumulated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (JCRSITE-44) Update contributor list
[ https://issues.apache.org/jira/browse/JCRSITE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13941334#comment-13941334 ] Tae Wong commented on JCRSITE-44: - There's no patch submitted to have the corrections committed. The name Jason Wagggoner has to be written as Waggoner. Update contributor list --- Key: JCRSITE-44 URL: https://issues.apache.org/jira/browse/JCRSITE-44 Project: Jackrabbit Site Issue Type: Improvement Reporter: Tae Wong The contributor list at: http://jackrabbit.apache.org/jackrabbit-team.html has some names which aren't accentuated (see the Jackrabbit contributors section). The first column is unaccentuated, the second column is accentuated. Juan Jose Vazquez Delgado, Juan José Vázquez Delgado Martin Koci, Martin Kočí (it's a Czech name...) Please accentuate these names. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (JCR-3754) [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload
[ https://issues.apache.org/jira/browse/JCR-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra reassigned JCR-3754: Assignee: Chetan Mehrotra [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload - Key: JCR-3754 URL: https://issues.apache.org/jira/browse/JCR-3754 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-data Affects Versions: 2.7.5 Reporter: Shashank Gupta Assignee: Chetan Mehrotra Fix For: 2.7.6 Attachments: JCR-3754.patch Currently s3 asynchronous uploads are not retried after failure. since failed upload file is served from local cache it doesn't hamper datastore functionality. During next restart all accumulated failed upload files are uploaded to s3 in synchronized manner. There should be retry logic for failed s3 asynchronous upload so that failed uploads are not accumulated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JCR-3755) Export S3DataStore package to enable osgi resolution
[ https://issues.apache.org/jira/browse/JCR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated JCR-3755: - Affects Version/s: 2.7.5 Export S3DataStore package to enable osgi resolution Key: JCR-3755 URL: https://issues.apache.org/jira/browse/JCR-3755 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-data Affects Versions: 2.7.5 Reporter: Amit Jain Assignee: Chetan Mehrotra Priority: Minor Fix For: 2.7.6 Attachments: JCR_3755.patch S3DataStore package org.apache.jackrabbit.ext.ds should be exported from the bundle so that osgi resolution is possible on bundles depending on this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JCR-3755) Export S3DataStore package to enable osgi resolution
[ https://issues.apache.org/jira/browse/JCR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated JCR-3755: - Fix Version/s: 2.7.6 Export S3DataStore package to enable osgi resolution Key: JCR-3755 URL: https://issues.apache.org/jira/browse/JCR-3755 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-data Affects Versions: 2.7.5 Reporter: Amit Jain Assignee: Chetan Mehrotra Priority: Minor Fix For: 2.7.6 Attachments: JCR_3755.patch S3DataStore package org.apache.jackrabbit.ext.ds should be exported from the bundle so that osgi resolution is possible on bundles depending on this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JCR-3755) Export S3DataStore package to enable osgi resolution
[ https://issues.apache.org/jira/browse/JCR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated JCR-3755: - Resolution: Fixed Status: Resolved (was: Patch Available) Applied a slightly modified patch in 1579543. * slf4j-api is required * DynamicImport-Package instruction was not correct. So fixed that Thanks for patch! Export S3DataStore package to enable osgi resolution Key: JCR-3755 URL: https://issues.apache.org/jira/browse/JCR-3755 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-data Affects Versions: 2.7.5 Reporter: Amit Jain Assignee: Chetan Mehrotra Priority: Minor Attachments: JCR_3755.patch S3DataStore package org.apache.jackrabbit.ext.ds should be exported from the bundle so that osgi resolution is possible on bundles depending on this. -- This message was sent by Atlassian JIRA (v6.2#6252)
