# Upload remapping is a bit too enthousiastic

**URL:** <https://meta.discourse.org/t/upload-remapping-is-a-bit-too-enthousiastic/118889>\
**Category:** Bug\
**Created:** [28.Май.2019 15:44:56 UTC](https://meta.discourse.org/t/upload-remapping-is-a-bit-too-enthousiastic/118889 "2019-05-28T15:44:56Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [30.Май.2019 07:52:24 UTC](https://meta.discourse.org/t/upload-remapping-is-a-bit-too-enthousiastic/118889/8 "2019-05-30T07:52:24Z")

</div>

> [@RGJ](#):
>
> getting more and more complicated and hard.

I do not think so, the moves will get **significantly** simpler. Walk the uploads table and upload all files to new s3 bucket, rebake and you are done.

They do though become more expensive computation wise cause a rebake is required.

This is a cost I think is worth bearing given we get a correct move at the end of the process. But, we have the flexibility of still doing database replace 🎢 as we do today for the `cooked` column and post revisions if that is how we roll, the key change in the process is that we leave `posts.raw` alone and then have 0% of corruption there. `posts.raw` and `posts_uploads` auto generated map will always be stable.

---

_[View the full topic](https://meta.discourse.org/t/upload-remapping-is-a-bit-too-enthousiastic/118889)._
