https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422015-05-19T17:30:00ZArvadosArvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=248382015-05-19T17:30:00ZWard Vandewegeward@curii.com
<ul><li><strong>Subject</strong> changed from <i>[API] walk api server installations and ensure modified_at for collections is unique</i> to <i>[API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is unique at the api level.</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/24838/diff?detail_id=24276">diff</a>)</li></ul> Arvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=248392015-05-19T17:31:23ZWard Vandewegeward@curii.com
<ul><li><strong>Subject</strong> changed from <i>[API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is unique at the api level.</i> to <i>[API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.</i></li></ul> Arvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=249142015-05-20T18:23:32ZBrett Smithbrett.smith@curii.com
<ul></ul><p>Isn't this easy enough to handle at the client level with filters like <code>modified_at >= current_working_modified_time, uuid not in [list of UUIDs I've already seen with that modified time]</code>?</p> Arvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=257282015-06-09T19:01:15ZTom Cleggtom@curii.com
<ul></ul><p>The goal here is to provide a safe and easy way for a client to get the next page of results. Note-3 is safe but not easy. Ensuring modified_at uniqueness helps make the "modified_at >= X" method safe, but even that is a bit awkward.</p>
<p>In order for "sort by modified_at" to be completely safe, we must guarantee at the database level that modified_at is not only unique, but greater than all other rows' modified_at values at the time of insert/update. Currently, modified_at is assigned by Rails model validations and (AFAIK) there is nothing in place to prevent updates from getting reordered between "assign modified_at" and "insert/update database record". <em>I think it's a good idea to enforce this constraint.</em></p>
<p>An even better solution would be for the server to provide a "next page token" which the client can send with its next request. This way the "next page" logic can sit on the server side instead of the client side, and the client doesn't need to know exactly which ordering guarantees are enforced. It can stick to "if the server doesn't give me a safe next-page link, I can't work."</p> Arvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=286162015-08-11T14:15:11ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Target version</strong> changed from <i>Bug Triage</i> to <i>Arvados Future Sprints</i></li></ul> Arvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=949892021-07-07T18:29:26ZWard Vandewegeward@curii.com
<ul><li><strong>Target version</strong> deleted (<del><i>Arvados Future Sprints</i></del>)</li></ul> Arvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=1122392023-02-14T22:24:38ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Release</strong> set to <i>60</i></li></ul> Arvados - Bug #6076: [API] walk api server installations and ensure modified_at for collections is unique + ensure modified_at is enforced to be unique at the api level.https://dev.arvados.org/issues/6076?journal_id=1235952024-03-01T21:15:57ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> set to <i>Future</i></li></ul>