1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
// Copyright 2015 Hyunsik Choi
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//! hdfs-rs is a library for accessing to HDFS cluster.
//! Basically, it provides libhdfs FFI APIs.
//! It also provides more idiomatic and abstract Rust APIs,
//! hiding manual memory management and some thread-safety problem of libhdfs.
//! Rust APIs are highly recommended for most users.
//!
//! ## Important Note
//! The original ``libhdfs`` implementation allows only one ``HdfsFs`` instance for the
//! same namenode because ``libhdfs`` only keeps a single ``hdfsFs`` entry for each namenode.
//! As a result, you need to keep a singleton ``HdfsFsCache`` in an entire program, and
//! you must get ``HdfsFs`` through only ``HdfsFsCache``. For it, you need to share
//! ``HdfsFsCache`` instance across all threads in the program.
//! Contrast, ``HdfsFs`` instance itself is thread-safe.
//!
//! ## Usage
//! in Cargo.toml:
//!
//! ```ignore
//! [dependencies]
//! hdfs = "0.0.4"
//! ```
//! or
//!
//! ```ignore
//! [dependencies.hdfs]
//! git = "https://github.com/hyunsik/hdfs-rs.git"
//! ```
//!
//! and this to your crate root:
//!
//! ```ignore
//! extern crate hdfs;
//! ```
//!
//! hdfs-rs uses libhdfs, which is JNI native implementation. JNI native implementation
//! requires the proper ``CLASSPATH``. exec.sh included in the source code root plays a role to
//! execute your program with the proper ``CLASSPATH``. ``exec.sh`` requires ``HADOOP_HOME``.
//! So, you firstly set ``HADOOP_HOME`` shell environment variable as follows:
//!
//! ```ignore
//! export HADOOP_HOME=<hadoop install dir>
//! ```
//!
//! Then, you can execute your program as follows:
//!
//! ```ignore
//! ./exec.sh your_program arg1 arg2
//! ```
//!
//! ## Testing
//! The test also requires the ``CLASSPATH``. So, you should run ``cargo test``
//! through ``exec.sh``.
//!
//! ```ignore
//! ./exec.sh cargo test
//! ```
//!
//! ## Example
//!
//! ```ignore
//! use std::rc::Rc;
//! use std::cell::RefCell;
//! use hdfs::HdfsFsCache;
//!
//! // You must get HdfsFs instance through HdfsFsCache. Also, HdfsFsCache
//! // must be shared across all threads in the entire program in order to
//! // avoid the thread-safe problem of the original libhdfs.
//! let cache = Rc::new(RefCell::new(HdfsFsCache::new()));
//! let fs: HdfsFs = cache.borrow_mut().get("hdfs://localhost:8020/").ok().unwrap();
//! match fs.mkdir("/data") {
//! Ok(_) => { println!("/data has been created") },
//! Err(_) => { panic!("/data creation has failed") }
//! };
//! ```
extern crate itertools;
extern crate libc;
extern crate log;
extern crate url;
pub use HdfsErr;
/// libhdfs native binding APIs
/// Rust APIs wrapping libhdfs API, providing better semantic and abstraction
pub use *;
/// Mini HDFS Cluster for easily building unit tests
pub use HdfsUtil;