[
https://issues.apache.org/jira/browse/HDDS-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-12918:
-------------------------------
Description:
Similar to HDDS-11699, we can move the byte range GET filter from S3G to the OM
so that the network and serialization cost can be reduced for objects with a
lot of blocks.
Applications like JuiceFS on S3 uses quite a bit of byte range fetch.
was:Similar to HDDS-11699, we can move the byte range GET filter from S3G to
the OM so that the network and serialization cost can be reduced for objects
with a lot of blocks.
> OM support byte range GET
> -------------------------
>
> Key: HDDS-12918
> URL: https://issues.apache.org/jira/browse/HDDS-12918
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM, s3gateway
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Similar to HDDS-11699, we can move the byte range GET filter from S3G to the
> OM so that the network and serialization cost can be reduced for objects with
> a lot of blocks.
> Applications like JuiceFS on S3 uses quite a bit of byte range fetch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
