https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422018-07-11T15:55:47ZArvadosArvados - Bug #13763: [API] groups#contents response should obey caller-provided order (not sort on type first)https://dev.arvados.org/issues/13763?journal_id=642672018-07-11T15:55:47ZTom Cleggtom@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/64267/diff?detail_id=61175">diff</a>)</li></ul> Arvados - Bug #13763: [API] groups#contents response should obey caller-provided order (not sort on type first)https://dev.arvados.org/issues/13763?journal_id=642682018-07-11T16:16:46ZTom Cleggtom@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/64268/diff?detail_id=61176">diff</a>)</li></ul><p>Suggest using a UNION query to get the desired set of UUIDs, then fetch the records as AR objects to return.</p> Arvados - Bug #13763: [API] groups#contents response should obey caller-provided order (not sort on type first)https://dev.arvados.org/issues/13763?journal_id=642882018-07-11T19:12:34ZTom Cleggtom@curii.com
<ul></ul><p>When <code>order=["name"]</code>, rows from tables without a name column should be sorted as if they had a null in the name column.</p>
TBD: Should we support the "groups.name" notation? Choices:
<ol>
<li>Return an error.</li>
<li>Return groups first (non-null names first, then null names), then non-group items.</li>
<li>Sort non-group items alongside the groups with null names. IOW, return groups with non-null names first, then fall back on subsequent/implicit/default orders for other object types and the remaining groups. <em>(seems most intuitive)</em></li>
</ol>
<p>The existing API ignores orders that are <em>not</em> prefixed by a table name.</p>
<p>However, the existing API accepts <em>filters</em> for both "groups.group_class" (meaning the filter does not affect types other than group) and "group_class" (meaning the filter applies to all types, and constitutes an error if a table is missing that column and is not excluded via "is_a" filter).</p>
<p>It might be less confusing if we also update the filtering behavior to match the new ordering behavior for unprefixed columns: i.e., for purposes of filtering, a nonexistent column is null.</p> Arvados - Bug #13763: [API] groups#contents response should obey caller-provided order (not sort on type first)https://dev.arvados.org/issues/13763?journal_id=652002018-08-01T15:52:16ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Target version</strong> set to <i>To Be Groomed</i></li></ul> Arvados - Bug #13763: [API] groups#contents response should obey caller-provided order (not sort on type first)https://dev.arvados.org/issues/13763?journal_id=942482021-07-06T21:10:14ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> deleted (<del><i>To Be Groomed</i></del>)</li></ul> Arvados - Bug #13763: [API] groups#contents response should obey caller-provided order (not sort on type first)https://dev.arvados.org/issues/13763?journal_id=1117842023-02-14T22:22:18ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Release</strong> set to <i>60</i></li></ul> Arvados - Bug #13763: [API] groups#contents response should obey caller-provided order (not sort on type first)https://dev.arvados.org/issues/13763?journal_id=1231662024-03-01T21:11:30ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> set to <i>Future</i></li></ul>