Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.3.0.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Trivial | DU refresh interval is not configurable* The 'du' (disk usage command from Unix) script refresh monitor is now configurable in the same way as its 'df' counterpart, via the property 'fs.du.interval', the default of which is 10 minute (in ms). | Major | Filesystem Implementation for OpenStack Swift* <!-- markdown --> Added file system implementation for OpenStack Swift. There are two implementation: block and native (similar to Amazon S3 integration). Data locality issue solved by patch in Swift, commit procedure to OpenStack is in progress. To use implementation add to core-site.xml following: ```xml <property> <name>fs.swift.impl</name> <value>com.mirantis.fs.SwiftFileSystem</value> </property> <property> <name>fs.swift.block.impl</name> <value>com.mirantis.fs.block.SwiftBlockFileSystem</value> </property> ``` In MapReduce job specify following configs for OpenStack Keystone authentication: ```java conf.set("swift.auth.url", "http://172.18.66.117:5000/v2.0/tokens"); conf.set("swift.tenant", "superuser"); conf.set("swift.username", "admin1"); conf.set("swift.password", "password"); conf.setInt("swift.http.port", 8080); conf.setInt("swift.https.port", 443); ``` Additional information specified on github: https://github.com/DmitryMezhensky/Hadoop-and-Swift-integration | Major | FixedLengthInputFormat and FixedLengthRecordReader* Addition of FixedLengthInputFormat and FixedLengthRecordReader in the org.apache.hadoop.mapreduce.lib.input package. These two classes can be used when you need to read data from files containing fixed length (fixed width) records. Such files have no CR/LF (or any combination thereof), no delimiters etc, but each record is a fixed length, and extra data is padded with spaces. The data is one gigantic line within a file. When creating a job that specifies this input format, the job must have the "mapreduce.input.fixedlengthinputformat.record.length" property set as follows myJobConf.setInt("mapreduce.input.fixedlengthinputformat.record.length",[myFixedRecordLength]); Please see javadoc for more details. | Major | Fix HTTPS support in HsftpFileSystem* Fix the https support in HsftpFileSystem. With the change the client now verifies the server certificate. In particular, client side will verify the Common Name of the certificate using a strategy specified by the configuration property "hadoop.ssl.hostname.verifier". | Major | Add a directbuffer Decompressor API to hadoop* Direct Bytebuffer decompressors for Zlib (Deflate & Gzip) and Snappy | Major | libhdfs doesn't return correct error codes in most cases* libhdfs now returns correct codes in errno. Previously, due to a bug, many functions set errno to 255 instead of the more specific error code. | Major | Implement HTTP policy for Namenode and DataNode* Add new HTTP policy configuration. Users can use "dfs.http.policy" to control the HTTP endpoints for NameNode and DataNode. Specifically, The following values are supported: HTTP\_ONLY : Service is provided only on http HTTPS\_ONLY : Service is provided only on https HTTP\AND\HTTPS : Service is provided both on http and https hadoop.ssl.enabled and dfs.https.enabled are deprecated. When the deprecated configuration properties are still configured, currently http policy is decided based on the following rules: If dfs.http.policy is set to HTTPS\ONLY or HTTP\AND\_HTTPS. It picks the specified policy, otherwise it proceeds to 2~4. It picks HTTPS\_ONLY if hadoop.ssl.enabled equals to true. It picks HTTP\AND\HTTPS if dfs.https.enable equals to true. It picks HTTP\_ONLY for other configurations. | Major | Numeric usernames do not work with WebHDFS FS* Add a new configuration property "dfs.webhdfs.user.provider.user.pattern" for specifying user name filters for WebHDFS. | Major | make the retry time and interval value configurable in openInfo()* Makes the retries and time between retries getting the length of the last block on file configurable. Below are the new configurations. dfs.client.retry.times.get-last-block-length dfs.client.retry.interval-ms.get-last-block-length They are set to the 3 and 4000 respectively, these being what was previously hardcoded. | Major | Change OP\_UPDATE\_BLOCKS with a new OP\_ADD\_BLOCK* Add a new editlog record (OP\ADD\BLOCK) that only records allocation of the new block instead of the entire block list, on every block allocation.