[docs] Update quickstart-flink doc to use kv.snapshot.interval 0s to avoid client obtain token issue

[luoyuxia]

Purpose

Linked issue: close #xxx
To fix client obtain token issue

Brief change log

Tests

API and Format

Documentation

[luoyuxia]

Unfortunately, we'll still need it. Otherwise, it'll throw exception

org.apache.fluss.exception.SecurityTokenException: Failed to get file access security token: The security token included in the request is invalid. (Service: AWSSecurityTokenService; Status Code: 403; Error Code: InvalidClientTokenId; Request ID: fabc25ae-dffb-43bf-af19-f2896f00d918; Proxy: null)

when client try to get sts token from server.
Similar to #2148

But to support it, we may need change the code the generate sts token in s3 filesystem.
See:
https://github.com/orgs/rustfs/discussions/1239

[wuchong]

@luoyuxia Thank you, could you open an issue in fluss to fix the way to generate sts token for s3?

[luoyuxia]

create in #2661

[luoyuxia]

we don't need to mount the iceberg plugin jar

[luoyuxia]

cc @wuchong @leekeiabstraction

[wuchong]

@luoyuxia Thank you, could you open an issue in fluss to fix the way to generate sts token for s3?

[wuchong]

Remove this line as well.

[leekeiabstraction]

@luoyuxia did you verify if this is an issue in Flink QuickStart?

I was able to make this work with Flink QuickStart.

It was only the paimon/iceberg one that was failing

[luoyuxia]

@wuchong Thanks for review. Comments addressed.

[luoyuxia]

@luoyuxia did you verify if this is an issue in Flink QuickStart?

I was able to make this work with Flink QuickStart.

It was only the paimon/iceberg one that was failing

If just follow the steps of Flink QuickStart. I won't meet this problem. But if I sumibit a sql to query all data of a primary key table, the issue will hapeen

[leekeiabstraction]

If just follow the steps of Flink QuickStart. I won't meet this problem. But if I sumibit a sql to query all data of a primary key table, the issue will hapeen

I see, maybe not as part of this PR, let's also try to add specific SQL query that cause the issue in? So that when we revisit this after fixing, we can naturally validate by running the additional query.

Thank you for catching!