Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature Request for Range support in Drive client.

Open
#7,817 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
google-cloud, java
Domain
api, cloud

Research direction

Start by locating the Drive client request API and reviewing how callers currently access or adjust HTTP headers for downloads. Verify how a byte range should be represented, then confirm that a request can send it and return the requested partial file stream without manual request modification.

Written by the indexing model from the issue text.

Description

priority: p4 type: feature request

Hello,
I am currently using the Drive client and I am trying to do a partial file download stored on a Google Drive account. After spending a few hours I found this as the solution to add the range to the HTTP header manually.

I was wondering if the Drive client could support adding the range header to the request itself. The reason is manually touching the HTTP request before sending it increases the likeliness of introducing a bug and generally forces me(the user of the client) to go deeper than I would like too. In general I would say that it is in within the scope of the client to support the adjustment of the HTTP headers being sent to the back-end.

As an example consider the S3Client that Amazon is currently exposing this.s3Client.getObject(this.getSkeleton.withRange(part.getStart(), part.getEnd()));. From here I would then actually execute the request and get a stream to that range of the file.

I am not sure if this is entirely out of scope or not so please let me know if this makes sense.
Thank you.

Dominant language
Java
Stars
725
Forks
394
Avg merge
42m
Merged PRs (30d)
257

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-api-java-client-services

All issues in googleapis/google-api-java-client-services

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.