Bug: creating a table on nonexistent s3 bucket can succeed but panic later.

[KeXiangWang]

Describe the bug

As titled

Error message/log

No response

To Reproduce

CREATE TABLE orders (
    order_id INT,
    order_date BIGINT,
    customer_name VARCHAR,
    price DECIMAL,
    product_id INT,
    order_status INT,
) WITH (
    connector = 's3_v2',
    match_pattern = 'sample_orders*',
    s3.region_name = 'us-east-1',
    s3.bucket_name = 'wkx-dynamodb',
    s3.credentials.access = 'XXXXXX',
    s3.credentials.secret = 'XXXXXX,
    s3.endpoint_url = 'https://s3.us-east-1.amazonaws.com'
) FORMAT PLAIN ENCODE CSV (
    without_header = 'false',
    delimiter = ','
);

All the info except bucket_name is correct. A thrown error is expected, rather than panic.

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

[github-actions]

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄