Adding Native Dali Data Loader support for TFRecord, Images, and NPZ files

[zhenghh04]

This PR is a partial merge of the following PR #81 @hariharan-devarajan

[zhenghh04]

@hariharan-devarajan , I pull part of your PR #81.
This only pull native_dali part. I have not pull native_torch and native_tensorflow. Still need more study to see whether there is a need to have native_torch and native_tensorflow.

For format, I keep only npz, npy, jpeg, png, hdf5. I don't have dlio_npz, etc. We can always determine whether it is dlio_npz or native_npz based on the data_loader selected.

[hariharan-devarajan]

Some potential improvements.

[zhenghh04]

@hariharan-devarajan I also have to removed the cache installation for DLIO, because of the code changes does not get push to the dlio installation, causing failing tests.

I think it is not good to keep cache for DLIO installation.

[zhenghh04]

@hariharan-devarajan Please review it again and check whether the changes look good to you.

[hariharan-devarajan]

@hariharan-devarajan I also have to removed the cache installation for DLIO, because of the code changes does not get push to the dlio installation, causing failing tests.

I think it is not good to keep cache for DLIO installation.

What if we split dependency installation with actual code installation?

The pip way to do this is.

python setup.py egg_info
pip install -r *.egg-info/requires.txt
rm -rf *.egg-info/

What do u think?

[hariharan-devarajan]

Some more minor comments.

[hariharan-devarajan]

@hariharan-devarajan Please review it again and check whether the changes look good to you.

Can u do the review again button. The commenting doesn’t notify me correctly.

[zhenghh04]

@hariharan-devarajan Please see all the comments again.

[hariharan-devarajan]

Almost there :)

[zhenghh04]

@hariharan-devarajan I also have to removed the cache installation for DLIO, because of the code changes does not get push to the dlio installation, causing failing tests.
I think it is not good to keep cache for DLIO installation.

What if we split dependency installation with actual code installation?

The pip way to do this is.

python setup.py egg_info
pip install -r *.egg-info/requires.txt
rm -rf *.egg-info/
``1

What do u think?

I think splitting dependency installation and actuall code installation will be good. New commit added this. commit 1f03159 and commit 5dd6ebf

[hariharan-devarajan]

The changes look good to me.