Releases: tencentyun/hadoop-cos
Releases · tencentyun/hadoop-cos
hadoop-cos v8.2.3
Features:
- support independent bucket configuration;
- support client-side encryption;
- change the class load of seekable write, avoid classNoDefine of Seekable class.
- add list parts to double-check upload part conflict;
ps: typically only use Hadoop-cos and cos_api-bundle pkg,
if you need to use the random write feature add the ofs-sdk-definition pkg,
if you need to use client-side encryption add the tencentcloud-sdk-java-kms and tencentcloud-sdk-java-common pkg.
hadoop-cos v8.2.2
fix:
- refactor: Modify the internal abort interface to adapt the hadoop-3.3.0 or later.
hadoop-cos v8.2.1
hadoop-cos v8.2.0
Features:
- support seekable write:
CosNSeekableFSDataOutputStream
implementingPosixSeekable
interface (requiresofs-sdk-definition-1.0.4.jar
); - support symbolic link;
- improve some code style and design;
hadoop-cos v8.1.8
hadoop-cos v8.1.7
Dependence: cos java sdk 5.6.69
Features:
- close range client when close file system
- fix: Try to create the temporary directory if it does not exits
- fix: fix the bug of the CosNByteBuffer put(byte) operation
- add configuartion to direct use ofs ranger when posix way query
- fs close check throw io exception
- style: revise the healthFlag of CosFileSystem
- add the dst create dir recursive check
hadoop-cos v8.1.6
Dependence: cos java sdk 5.6.69
Features:
- pass through the ranger policy URL and auth Etag to POSIX bucket which used the ofs java SDK mount fs.
- change the order of init real file system, avoid classNodef error when not use POSIX bucket.
- add the configurations of the list max key size.
hadoop-cos v8.1.5
Dependence: cos java sdk 5.6.69
Features:
- support fs.cosn.flush.enabled(default true) to close flush data to cos
- support fs.cosn.map_disk.delete_on_exit.enabled(default true) to disable the map disk channel file delete on exit
hadoop-cos v8.1.4
Dependence: cos java sdk 5.6.69
Features:
- Fix CosNByte buffer bug which may occurs wrong position of the output stream and cause the consistent check to go wrong. may Influence version from v8.0.0 to v8.1.3.