https://discord.cloudflare.com logo
Join Discord
Powered by
# r2
  • s
    They'll post a message in either here or #909458221419356210 channel on this discord and you need to reply to that. Or if you're on enterprise plan your account manager might be able to get it setup
  • k
    there will be instructions in the message, not really a reply (just read it, you will understand)
  • k
  • s
    Still don’t have R2 access
  • m
  • v
    Not really sure yet. Could be a while. Unlike S3, R2 doesn't have egress. So you could just as easily write a select-like Worker and there's not really any perf/cost impact vs us supporting it natively
  • l
    my weekend project: write a worker SQL to R2 Translator /joke_switch
  • v
    I didn't mean to imply it would be a trivial amount of work. I wonder if there's something that can be cobbled together from the NPM ecosystem with JQ. The SQL parsing would be the most annoying bit
  • v
    (although doing things efficiently in a streaming fashion would be the second most annoying bit)
  • l
    hmm
  • i
    Quick question about Multipart uploads (this also might apply to S3... not sure), is there a timeout between uploading and confirming final upload? For example: I have an upload that also needs a DB write. Can I start the multipart upload, upload all my parts, then do my database read, then commit? Is there a timeout between my final part upload and commit there?
  • e
    I don't know about R2, but S3 is immediately consistent - as soon as you finished PUT'ing the object, it becomes immediately persisted & available. This wasn't always true and cause difficult bugs while working with S3, but now AWS guarantees immediate consistency.
  • k
  • i
    Yeah, but I just mean on multipart uploads.
  • i
    For example.
  • i
    If I have a multipart upload in 20 parts, and I send all 20, then do a database query before I confirm the transfer, will there be a timeout I might hit if my database query takes too long?
  • i
    (Between the final part #20 upload and the confirmation?)
  • a
    you should do your db write after the completion request
  • a
    your application code should not try to do a db write prior to the completion request finishing
  • v
    Hey folks! Can we use same R2 bucket from different Cloudflare workers? Let's say, one to write and other to read? Will we be able to bind it to both workers? Or perhaps we will need to http and proxy response on get side?
  • w
    You can yep
  • i
    So my main concern with that was that the DB request might not go through.
  • i
    So I upload a file, confirm it, then my DB request fails and I'm forced to roll back.
  • i
    Whereas if I do the DB request, then the confirmation I can rollback the upload if my DB request fails.
  • a
    why would you need to roll back the upload
  • a
    i mean wouldnt you just reissue the db query that had timed out?
  • i
    No, not the DB query timeout.
  • i
    Let me see if I can explain a bit more.
  • i
    So I have a DB INSERT that may or may not fail, depending on a variety of external factors.
  • i
    And I have a file that needs to be in sync with the DB.
1...353637...1050Latest