blackfaced opened a new issue, #8205:
URL: https://github.com/apache/gravitino/issues/8205
### Describe the feature
When debugging a fileset locally using the Python client as described in
Gravitino documentation, I found that the s3_endpoint option in the options
dictionary does not take effect. Even after setting s3_endpoint to an external
address, the client still tries to connect to the internal endpoint.
For example, I set:
```python
options = {
"s3_endpoint": "https://external-s3-endpoint.com/";,
...
}
```
But the error message shows the client is still trying to connect to the
internal endpoint:
Connect timeout on endpoint URL: "https://internal-s3-endpoint.com/xxxxxx";
it seems that gravitino uses catalog_props first, then check for options
<img width="2396" height="866" alt="Image"
src="https://github.com/user-attachments/assets/0da2a267-f82b-48b4-b83b-2df397320f99";
/>
I hope that there is a way to override the s3_endpoint in catalog_props, so
that I can use it in different environment.
### Motivation
on cloud environment, there is inner endpoint and public endpoint, inner
endpoint is fast and cheap, public endpoint is slow and expensive, both has use
cases
### Describe the solution
_No response_
### Additional context
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
