feat(services): add hdfs native layout

[shbhmrzd]

For #3144

[shbhmrzd]

@Xuanwo
Please review the layout.
Will move ahead with the implementation post that.

[Xuanwo]

Mostly LGTM, we can begin our journey now!

[Xuanwo]

Hi, we need to address this error:

error[E0631]: type mismatch in function arguments
   --> core/src/services/hdfs_native/backend.rs:190:22
    |
190 |             .map_err(new_std_io_error)?;
    |              ------- ^^^^^^^^^^^^^^^^ expected due to this
    |              |
    |              required by a bound introduced by this call
    |
   ::: core/src/raw/std_io_util.rs:27:1
    |
27  | pub fn new_std_io_error(err: std::io::Error) -> Error {
    | ----------------------------------------------------- found signature defined here
    |
    = note: expected function signature `fn(hdfs_native::HdfsError) -> _`
               found function signature `fn(std::io::Error) -> _`

We can implement a parse_hdfs_error instead.

[shbhmrzd]

Hi, we need to address this error:

error[E0631]: type mismatch in function arguments
   --> core/src/services/hdfs_native/backend.rs:190:22
    |
190 |             .map_err(new_std_io_error)?;
    |              ------- ^^^^^^^^^^^^^^^^ expected due to this
    |              |
    |              required by a bound introduced by this call
    |
   ::: core/src/raw/std_io_util.rs:27:1
    |
27  | pub fn new_std_io_error(err: std::io::Error) -> Error {
    | ----------------------------------------------------- found signature defined here
    |
    = note: expected function signature `fn(hdfs_native::HdfsError) -> _`
               found function signature `fn(std::io::Error) -> _`

We can implement a parse_hdfs_error instead.

Sure will take care of it

[Xuanwo]

Hi, please make sure previous commits pass the CI before adding 9e34b5f. You can return an unsupported error instead.

[Xuanwo]

I think it's best to merge the layouts first, then add the detailed implementations.

[shbhmrzd]

I think it's best to merge the layouts first, then add the detailed implementations.

Sure, let me revert this change.

[Xuanwo]

Let's address the CI issues individually, particularly those found at https://github.com/apache/incubator-opendal/actions/runs/7541144383/job/20527241562?pr=3933.

First of all, running cargo fmt to make sure code is formatted.
And than, running cargo clippy --all-targets --features=services-hdfs-native to make sure all newly added code pass the check of clippy.

[shbhmrzd]

Should I push Cargo.lock file as well ?

[Xuanwo]

Should I push Cargo.lock file as well ?

Yes. Changes to lock file should also be committed.

[Xuanwo]

Let's rock!

[shbhmrzd]

@Xuanwo Thank you so much for your patience and guidance 🙇

[Xuanwo]

@Xuanwo Thank you so much for your patience and guidance 🙇

Have fun!