org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.config

gistfile1.txt

file ::= (comment) (header) *
comment ::= '#' <any>
header ::= prop '=' value
prop ::= symbolic-name // 1.4.2 of OSGi Core Specification
symbolic-name ::= token { '.' token } 
token ::= { [ 0..9 ] | [ a..z ] | [ A..Z ] | '_' | '-' }
value ::= [ type ] ( '[' values ']' | '(' values ')' | simple ) 
values ::= simple { ',' simple } 
simple ::= '"' stringsimple '"'
type ::= <1-char type code>
stringsimple ::= <quoted string representation of the value> (see below)
The 1 character type code is one of:

'T' : simple string
'I' : Integer
'L' : Long
'F' : Float
'D' : Double
'X' : Byte
'S' : Short
'C' : Character
'B' : Boolean


https://repo.adobe.com/nexus/content/groups/public/com/adobe/granite/com.adobe.granite.oak.s3connector/


accessKey: The AWS access key.

secretKey: The AWS secret access key.

s3Bucket: The bucket name.

s3Region: The bucket region.

path: The path of the data store. The default is <AEM install folder>/repository/datastore

minRecordLength: The minimum size of an object that should be stored in the data store. The default is 16KB.

maxCachedBinarySize: Binaries with size less than or equal to this size will be stored in memory cache. The size is in bytes. The default is 17408 (17 KB).

cacheSize: The size of the cache. The value is specified in bytes. The default is 64GB.

secret: Only to be used if using binaryless replication for shared datastore setup.

stagingSplitPercentage: The percentage of cache size configured to be used for staging asynchronous uploads. The default value is 10.

uploadThreads: The number of uploads threads that are used for asynchronous uploads. The default value is 10.

stagingPurgeInterval: The interval in seconds for purging finished uploads from the staging cache. The default value is 300 seconds (5 minutes).

stagingRetryInterval: The retry interval in seconds for failed uploads. The default value is 600 seconds (10 minutes).

The DataStore implementations of S3DataStore, CachingFileDataStore and AzureDataStore support local file system caching. The CachingFileDataStore implementation is useful when the DataStore is on NFS (Network File System).