Can't create iceberg source using MinIO and Hive Metastore.

[viethqb]

Describe the bug

I use risingwave on k8s with config:

---
apiVersion: risingwave.risingwavelabs.com/v1alpha1
kind: RisingWave
metadata:
  name: risingwave
  namespace: dataplatform
spec:
  # frontendServiceType: NodePort
  image: risingwavelabs/risingwave:v2.0.0
  metaStore:
    etcd:
      endpoint: operator-etcd:2379
  stateStore:
    dataDirectory: risingwave
    minio:
      credentials:
        secretName: minio-credentials
      bucket: dataplatform
      endpoint: https://minio.xxx.xxx.xxx
  components:
    meta:
      nodeGroups:
        - replicas: 1
          name: ""
          template:
            spec:
              volumes:
                - name: heap
                  emptyDir:
                    sizeLimit: 1Gi
              volumeMounts:
                - mountPath: /heap
                  name: heap
              env:
                - name: MALLOC_CONF
                  value: prof:true,lg_prof_interval=-1,lg_prof_sample=20,prof_prefix:/heap/
                - name: RW_HEAP_PROFILING_DIR
                  value: /heap
              # resources:
              #   limits:
              #     cpu: 1
              #     memory: 2Gi
              #   requests:
              #     cpu: 1
              #     memory: 2Gi
    compactor:
      nodeGroups:
        - replicas: 1
          name: ""
          template:
            spec:
              volumes:
                - name: heap
                  emptyDir:
                    sizeLimit: 1Gi
              volumeMounts:
                - mountPath: /heap
                  name: heap
              env:
                - name: MALLOC_CONF
                  value: prof:true,lg_prof_interval=-1,lg_prof_sample=20,prof_prefix:/heap/
                - name: RW_HEAP_PROFILING_DIR
                  value: /heap
    frontend:
      nodeGroups:
        - replicas: 1
          name: ""
          template:
            spec:
              # resources:
                # limits:
                #   cpu: 1
                #   memory: 2Gi
                # requests:
                #   cpu: 1
                #   memory: 2Gi
    compute:
      nodeGroups:
        - replicas: 1
          name: ""
          template:
            spec:
              volumes:
                - name: heap
                  emptyDir:
                    sizeLimit: 1Gi
              volumeMounts:
                - mountPath: /heap
                  name: heap
              env:
                - name: MALLOC_CONF
                  value: prof:true,lg_prof_interval=-1,lg_prof_sample=20,prof_prefix:/heap/
                - name: RW_HEAP_PROFILING_DIR
                  value: /heap
              # resources:
              #   limits:
              #     cpu: 2
              #     memory: 4Gi # Memory limit will be set to `RW_TOTAL_MEMORY_BYTES`
              #   requests:
              #     cpu: 2
              #     memory: 4Gi

I create iceberg source with the following sql statement:

create source source_demo_hive
with (
    connector = 'iceberg',
    catalog.type = 'hive',
    catalog.uri = 'thrift://hive-metastore:9083',
    warehouse.path = 's3://dataplatform/lakehouse/',
    s3.endpoint = 'https://minio.xxx.xxx.xxx',
    s3.access.key = 'xxxxxxxxxx',
    s3.secret.key = 'xxxxxxxxxxx',
    s3.region = 'ap-southeast-1',
    catalog.name = 'lakehouse',
    database.name = 'demo',
    table.name = 'demo_table'
); 

1. ERROR 1: Unable to load region from system settings. Region must be specified either via environment variable (AWS_REGION) => config s3.region = 'ap-southeast-1' not worked => I workaroud by creating environment variables AWS_REGION=ap-southeast-1
2. ERROR 2: After passing error 1 => Caused by: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: dataplatform.minio.xxx.xxx.xxx => Path-style URL access must be enabled => This config is not available

Expectation:

1. Fix s3.region not working
2. add config s3.path.style.access for iceberg source.

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response