If I'm understanding you correctly, the error will stop only after all three dbs' schemas are changed. Since I've only updated some of the servers, and since some dbs are on the upgraded servers and some dbs are on the old servers, I will keep receiving this error until I upgrade the remaining servers and wait for the schemas to change. Is that correct?
What about if I just patch _really_merge_items in swift/account/backend.py and add the line
If I'm understanding you correctly, the error will stop only after all three dbs' schemas are changed. Since I've only updated some of the servers, and since some dbs are on the upgraded servers and some dbs are on the old servers, I will keep receiving this error until I upgrade the remaining servers and wait for the schemas to change. Is that correct?
What about if I just patch _really_merge_items in swift/account/ backend. py and add the line
rec. setdefault( 'storage_ policy_ index', 0) # legacy
That should handle the case of rows that are missing the 'storage_ policy_ index' column without requiring me to upgrade all servers at once. Right?