jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-56) File system abstraction
Date Tue, 10 Apr 2012 14:45:16 GMT

    [ https://issues.apache.org/jira/browse/OAK-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250702#comment-13250702
] 

Thomas Mueller commented on OAK-56:
-----------------------------------

> this would only be needed by a specific MK implementation

Sure.

> foreseeable MK implementations are explicitly not directly based on the file system

Actually, that's not correct: the default data store is file based,
and there is a plan to create a file based persistence manager within Adobe.

> so far i didn't have a need for encryption, 
> zip file support etc in the current microkernel implementation.

Probably you didn't know that customers were asking for such features,
and you didn't know about existing features within Day CRX. 
Among the feature already supported are:

* detection and special behavior of out-of-disk space situation
* profiling and statistics over JMX
* caching (improved performance)
* testing: simulating out of disk space and out of memory 
  (ensure the repository doesn't corrupt in this case)

Requested features are:

* re-try on file system problems
* encryption
* file system monitoring
* replication / real-time backup on the file system level (for clustering)
* allows to implement s3 / hadoop / mongodb / ... file systems

Additional features that would be nice for development:

* debugging (for example, logging all file system operations)
* testing: simulate very large files (using an in-memory file system)


                
> File system abstraction
> -----------------------
>
>                 Key: OAK-56
>                 URL: https://issues.apache.org/jira/browse/OAK-56
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mk
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>
> A file system abstraction allows to add new features (cross cutting concerns) in a modular
way, for example:
> - detection and special behavior of out-of-disk space situation
> - profiling and statistics over JMX
> - re-try on file system problems
> - encryption
> - file system monitoring
> - replication / real-time backup on the file system level (for clustering)
> - caching (improved performance for CRX)
> - allows to easily switch to faster file system APIs (FileChannel, memory mapped files)
> - debugging (for example, logging all file system operations)
> - allows to implement s3 / hadoop / mongodb / ... file systems - not only by us but from
3th party, possibly the end user
> - zip file system (for example to support read-only, compressed repositories)
> - testing: simulating out of disk space and out of memory (ensure the repository doesn't
corrupt in this case)
> - testing: simulate very large files (using an in-memory file system)
> - splitting very large files in 2 gb blocks (FAT and other file systems that don't support
large files)
> - data compression (if needed)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message