feat: Set up integration tests

[bokket]

Signed-off-by: bokket [email protected]

[xxchan]

ditto

[xxchan]

ditto (or assert.NoError)

[xxchan]

Similarly for code below

[Xuanwo]

I think it's a bug in setup-hdfs: https://github.com/beyondstorage/setup-hdfs/pull/36/checks?check_run_id=3450465739

I will try to fix it tomorrow.

[Xuanwo]

Hello, I fixed this problem in beyondstorage/setup-hdfs#36, please test it again:

steps:
  - uses: actions/setup-python@v2
    with:
      python-version: '3.8'
  - uses: actions/setup-java@v1
    with:
      java-version: '11'

  - uses: beyondstorage/setup-hdfs@master
    with:
      hdfs-version: '3.3.1'

  - run: curl ${{ env.HDFS_NAMENODE_ADDR }}

[Xuanwo]

Ops, let's test on linux only for now.

[Xuanwo]

We can test on more supported versions like:

• "2.10.1"
• "2.2.2"
• "3.3.0"
• "3.3.1"

[bokket]

I try to add more versions, just like:
hdfs: [ "2.10.1", "2.2.2", "3.3.0", "3.3.1"],but look like failure :)
It just had the wrong version number.I have fixed it.
"2.2.2"--->"3.2.2"

[Xuanwo]

How about sending a PR to setup-hdfs to fix it?

[Xuanwo]

Starting namenodes on [localhost]
localhost: Host key verification failed.
localhost: Host key verification failed.
Starting secondary namenodes [0.0.0.0]
0.0.0.0: Host key verification failed.

Strange, let's try to figure it out.

[bokket]

Starting namenodes on [localhost]
localhost: Host key verification failed.
localhost: Host key verification failed.
Starting secondary namenodes [0.0.0.0]
0.0.0.0: Host key verification failed.

Strange, let's try to figure it out.

I conducted experiments in my own warehouse and found a very interesting problem：
The version of "2.10.1" always seems to reject connection.

[Xuanwo]

Great work!