[hotfix] [connectors/hbase] Fix equal method of HBaseWriteOptions

[LiebingYu]

What is the purpose of the change

The equals method of HBaseWriteOptions uses == to determine whether the parallelism of the Integer type is equal, which will cause problems.

The relevant code is as follows.

    private final Integer parallelism;

    public boolean equals(Object o) {
        ....
        return bufferFlushMaxSizeInBytes == that.bufferFlushMaxSizeInBytes
                && bufferFlushMaxRows == that.bufferFlushMaxRows
                && bufferFlushIntervalMillis == that.bufferFlushIntervalMillis
                && parallelism == that.parallelism;
    }

In order to avoid similar problems, I refer to HBaseLookupOptions and use Objects.equals() uniformly to judge whether the internal member variables are equal.

Brief change log

• The equals method of HBaseWriteOptions

Verifying this change

This change is already covered by existing tests.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)

[flinkbot]

CI report:

• 6499e3a Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[snuyanzin]

@LB-Yu thanks for your contribution

The Flink HBase connector resides in it's own repository nowadays, if this code change is still relevant, please open the PR in https://github.com/apache/flink-connector-hbase/