Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-4018

Consistent Async Upload Executor handling in Backend implementations

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.13.4, 2.14
    • Component/s: None
    • Labels:

      Description

      There are some inconsistent configuration/behaviors regarding asynchronous upload executor handling.
      For example,

      • VFSBackend disables async upload based on asyncPoolSize not based on CachingDataStore#asyncUploadLimit.
      • FSBackend disables it based on CachingDataStore#asyncUploadLimit correctly as of JCR-4008.
      • S3Backend doesn't have a feature to disable async uploading yet.

      Probably it would be nicer to have AbstractBackend for all the practical Backend implementations to share the handling on asynchronous uploading features such as how to create an Executor and async executor pool size, etc. There are already some duplicate code regarding this in VFSBackend and FSBackend.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                amitjain Amit Jain
                Reporter:
                woon_san Woonsan Ko
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: