| 接口 | 说明 |
|---|---|
| BlockReader |
The API shared between local and remote block readers.
|
| 类 | 说明 |
|---|---|
| ByteRangeInputStream |
To support HTTP byte streams, a new connection to an HTTP server needs to be
created each time.
|
| ByteRangeInputStream.URLOpener |
This class wraps a URL and provides method to open connection.
|
| ChecksumDistributedFileSystem |
An implementation of ChecksumFileSystem over DistributedFileSystem.
|
| DFSClient |
DFSClient can connect to a Hadoop Filesystem and
perform basic file tasks.
|
| DFSClient.DFSDataInputStream |
The Hdfs implementation of
FSDataInputStream |
| DFSClient.RemoteBlockReader |
This is a wrapper around connection to datadone
and understands checksum, offset etc
|
| DFSClient.Renewer | |
| DFSConfigKeys |
This class contains constants for configuration keys used
in hdfs.
|
| DFSUtil | |
| DFSUtil.StaleComparator |
Comparator for sorting DataNodeInfo[] based on stale states.
|
| DistributedFileSystem |
Implementation of the abstract FileSystem for the DFS system.
|
| DistributedFileSystem.DiskStatus | |
| HDFSPolicyProvider |
PolicyProvider for HDFS protocols. |
| HftpFileSystem |
An implementation of a protocol for accessing filesystems over HTTP.
|
| HftpFileSystem.TokenManager | |
| HsftpFileSystem |
An implementation of a protocol for accessing filesystems over HTTPS.
|
| HsftpFileSystem.DummyHostnameVerifier |
Dummy hostname verifier that is used to bypass hostname checking
|
| HsftpFileSystem.TokenManager |
A distributed implementation of FileSystem. This is loosely modelled after
Google's GFS.
The most important difference is that unlike GFS, Hadoop DFS files have strictly one writer at any one time. Bytes are always appended to the end of the writer's stream. There is no notion of "record appends" or "mutations" that are then checked or reordered. Writers simply emit a byte stream. That byte stream is guaranteed to be stored in the order written.
Copyright © 2009 The Apache Software Foundation