Skip to content

new feature: Allow setting Content-Encoding in GCS (at least when writing) #5607

@wlinna

Description

@wlinna

Feature Description

Google Cloud Storage supports setting Content-Encoding, but for some reason this has not been implemented in OpenDAL. Not having support for Content-Encoding means that I have to use other library just so that I can set the header while uploading

Problem and Solution

With Content-Encoding supported, I could use OpenDAL to upload my zstd / brotli / gzip -compressed assets to Google Cloud Storage and use them normally (such as download with a browser and have them decompressed automatically)

Additional Context

No response

Are you willing to contribute to the development of this feature?

  • Yes, I am willing to contribute to the development of this feature.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions