Skip to content

Set initial metadata file on first upload #363

Closed
Closed
Set initial metadata file on first upload#363
Assignees
temka1234
Labels
🚨This issue needs some love.api: storageIssues related to the Cloud Storage API.triage meI really want to be triaged.
Milestone
Storage Stable

Description

@temka1234
temka1234
opened on Jan 27, 2015

In my project i want to create an empty file in google storage with metadata in one step.
I found this note in gcloud-node/lib/storage/file.js:

...
 * @param {object=} metadata - Metadata to set on the object. This is useful
 *     when you are creating a file for the first time, to prevent making an
 *     extra call to `setMetadata`.
...
function File(bucket, name, metadata) { }

But i cant find any code that use file.metadata parameter in createWriteStream or getWritableStream_.
Also storage.bucket.file(name) method that created new instance of File not contains metadata parameter.

I know, that i can use createWriteStream(metadata). This is the only way?

Activity

  1. stephenplusplus commented on Jan 27, 2015

    @stephenplusplus
    stephenplusplus
    on Jan 27, 2015
    Contributor

    The File constructor taking a metadata argument is a relic of old code, I believe.

    The problem is, creating a File instance (ex: through storage.bucket.file()) shouldn't have any async/api effects. So, it would be confusing if you said...

    var file = myBucket.file('file-name', { metaprop: 'value' })
file.getMetadata(function(err, metadata) { /* no metaprop here */ })

    ...because the metadata you "set" wasn't actually set.

    Instead, you can explicitly set metadata on a file:

    var file = myBucket.file('file-name')
file.setMetadata({ metaprop: 'value' }, function(err, metadata) {})

    Or use bucket.upload: http://googlecloudplatform.github.io/gcloud-node/#/docs/v0.12.0/storage/bucket?method=upload

  2. temka1234 commented on Jan 28, 2015

    @temka1234
    temka1234
    on Jan 28, 2015
    Author

    Thanks for the reply!

  3. temka1234
    closed this as completedon Jan 28, 2015
  4. jgeewax
    added
    api: storageIssues related to the Cloud Storage API.
    enhancement
    on Feb 2, 2015
  5. jgeewax
    added this to the Storage Stable milestone on Feb 2, 2015
  6. yoshi-automation
    added
    🚨This issue needs some love.
    triage meI really want to be triaged.
    on Apr 6, 2020
  7. JustinBeckwith
    assigned
    temka1234
    on Feb 1, 2021
  8. chingor13
    added a commit that references this issue on Aug 22, 2022

    chore: update generated protos.js (#363)

    9106c49
  9. sofisl
    added a commit that references this issue on Sep 16, 2022

    build: add Node 8 tests (#363)

    f6748d3
  10. sofisl
    added 4 commits that reference this issue on Oct 5, 2022

    build: add Node 8 tests (#363)

    987c5b1

    build: add Node 8 tests (#363)

    31f1537

    build: add Node 8 tests (#363)

    9829f1a

    feat: move ts target to es2018 from es2016 (#363)

    217009e

  11. 24 remaining items

  12. sofisl
    added 2 commits that reference this issue on Feb 3, 2026

    chore: make test prefix unique per run (#363)

    4764022

    chore(deps): update dependency google-proto-files to ^0.19.0 (#363)

    c972597
  13. GautamSharda
    added a commit that references this issue on Feb 5, 2026

    build: add configuration for automated doc deployment (#363)

    061c0b6
  14. sofisl
    added a commit that references this issue on Feb 17, 2026

    chore(deps): update dependency google-proto-files to ^0.19.0 (#363)

    70d985c
  15. GautamSharda
    added a commit that references this issue on Feb 23, 2026

    build: add configuration for automated doc deployment (#363)

    59057b8
  16. sofisl
    added a commit that references this issue on Feb 25, 2026

    Remove unused dependencies (#363)

    f089177
  17. GautamSharda
    added 2 commits that reference this issue on Feb 25, 2026

    chore(deps): update dependency jsdoc-region-tag to v3 (#363)

    f38d9a9

    build: add configuration for automated doc deployment (#363)

    f3beec1
  18. sofisl
    added 2 commits that reference this issue on Feb 26, 2026

    Release @google-cloud/spanner v2.1.0 (#363)

    e2ae536

    chore: migrate code from googleapis/gcp-metadata (#53)

    fa9a454
  19. thiyaguk09
    added a commit that references this issue on Mar 18, 2026

    Remove unused dependencies (googleapis#363)

    fe1223c
  20. GautamSharda
    added 2 commits that reference this issue on Mar 23, 2026

    chore: drop contributors from multiple places (#363)

    21b399e

    chore: drop contributors from multiple places (#363)

    5e1180d
  21. shivanee-p
    added a commit that references this issue on Mar 27, 2026

    chore: drop contributors from multiple places (#363)

    cd140bb
  22. thiyaguk09
    added a commit that references this issue on May 5, 2026

    chore: drop contributors from multiple places (googleapis#363)

    85744de
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.api: storageIssues related to the Cloud Storage API.triage meI really want to be triaged.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions