3.6.0
Release Notes
New Features and Enhancements
Functional
-
The new simple way to use a custom scripting engine either a storage
driver implementation. Just put the extension jar file(s) into the
ext
directory of Mongoose and it's ready to use. -
JSR-223 Compliant Scenario Engine
Powerful scripting capability using any language supporting JSR-223
standard. Javascript is proposed as default scenarios language.
Non-functional
-
All storage driver implementations moved to the separate projects
under the same GitHub organization.
The list of the storage drivers supported currently:- EMC Atmos
- EMC S3 (extensions)
- Filesystem
- HDFS (new)
- NFS (not working currently, under development)
- Amazon S3 (generic)
- OpenStack Swift
The deployment procedure significantly changed,
so please keep attention on this. Note also that base/core mongoose
distribution doesn't include any storage driver implementation since
the new version. -
The connection pool used by Mongoose moved to the separate project
netty-connection-pool. -
The source code repository name changed from
mongoose
to
mongoose-base
due to storage driver implementations separation.
Accessing via the old name redirects to the new one. -
Moved all content example files and all scenario files under the
commonexample
directory. -
Changed the default new items name length to 12 characters in
order to make the new item name characters distribution uniform (in
the space of the default radix of 36: [0-9a-z]). Previously all new
item names began with character "0" either "1" what was not uniform
enough.
Fixed Bugs
- (1120) Path items input doesn't finish the listing
- (1147) Connection pool deadlock if a connection is dropped
Documentation
- Deployment
- User Guide
- Troubleshooting
- Reference