JindoSDK resolves the OSS-HDFS endpoint from three sources in priority order: the access path, then bucket-level configuration, then global configuration. Choose the method that matches your access path format.
| Access path format | Endpoint source |
|---|---|
oss://<Bucket>.<Endpoint>/<Object> |
Embedded in the path (Method 1, recommended) |
oss://<Bucket>/<Object> |
core-site.xml: bucket-level (Method 2) or global (Method 3) |
Method 1: Embed the endpoint in the access path (recommended)
Include the endpoint directly in the access path using the format oss://<Bucket>.<Endpoint>/<Object>. JindoSDK reads the endpoint from the path and routes requests to OSS-HDFS automatically. No additional configuration is required.
Example:
oss://example-oss-bucket.cn-shanghai.oss-dls.aliyuncs.com/TestMethod 2: Configure a bucket-level endpoint
If your access path uses the oss://<Bucket>/<Object> format, add a bucket-level endpoint to core-site.xml. A bucket-level setting overrides the global endpoint for that bucket.
<configuration>
<property>
<name>fs.oss.bucket.<bucket-name>.endpoint</name>
<value>cn-xxx.oss-dls.aliyuncs.com</value>
</property>
</configuration>Replace <bucket-name> with your OSS-HDFS bucket name.
If no bucket-level endpoint is configured, JindoSDK falls back to the global endpoint (Method 3).
Method 3: Configure a global endpoint
Add a global endpoint to core-site.xml as the default for all oss:// requests. Use this method if you want to access OSS-HDFS by default.
<configuration>
<property>
<name>fs.oss.endpoint</name>
<value>cn-xxx.oss-dls.aliyuncs.com</value>
</property>
</configuration>