https://pulp.plan.io/https://pulp.plan.io/favicon.ico2018-01-05T15:30:59ZPulpPulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=236862018-01-05T15:30:59Zdaviddavis
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23686/diff?detail_id=24147">diff</a>)</li></ul> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=236872018-01-05T15:31:31Zdaviddavis
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23687/diff?detail_id=24148">diff</a>)</li></ul> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=236912018-01-05T15:47:55Zdalleydalley@redhat.com
<ul><li><strong>Tracker</strong> changed from <i>Issue</i> to <i>Story</i></li><li><strong>% Done</strong> set to <i>0</i></li></ul> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=236942018-01-05T15:49:46Zdaviddavis
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23694/diff?detail_id=24155">diff</a>)</li></ul> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=250422018-03-08T14:48:07Zmilan
<ul><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul><p>LGTM; let's just decide (on the sprint planning) about the field naming i.e <code>_href_in_list</code> vs <code>href_in_list</code></p> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=271832018-04-03T16:11:10Zdaviddavis
<ul><li><strong>Sprint Candidate</strong> deleted (<del><i>Yes</i></del>)</li></ul> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=274022018-04-11T15:16:17Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Sprint Candidate</strong> set to <i>No</i></li><li><strong>Tags</strong> deleted (<del><i>Pulp 3 MVP</i></del>)</li></ul> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=274842018-04-13T18:26:10Zdalleydalley@redhat.com
<ul></ul><ul>
<li>What should the name of the field be? href_in_list or id_in_list?</li>
</ul>
<p>The name of the field should be "href and it should support the "exact" and "in" filters. This would allow you to filter on a list of hrefs with the query "/?href__in=<href1>,<href2></p>
<p>My filter overhaul recently did something similar with all of the existing filters, e.g. "/?name__in=foo,foo2". It also works for hrefs, though, and I implemented "content__in" to search for repo versions containing multiple content hrefs.</p> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=275452018-04-17T20:52:31Zdalleydalley@redhat.com
<ul></ul><p>So I thought about this a bit more and I think we should try to nail down some actual use cases for this functionality.</p>
<p>The main purpose of filtering is a human-friendly way of figuring out which objects meet certain human-facing criteria. In order to obtain your list of HREFs you're probably doing some other filter operation first, using dates or names or numbers or online=True or something. But in that case, you could just combine your filters together instead of trying to extract the HREFs and then do a separate filter operation on those HREFs.</p>
<p>e.g. instead of doing</p>
<pre><code>/repository/<uuid>/versions/?number__gte=5
{
blah blah blah
}
HREFS go into new filter
repository/<uuid>/versions/?content=<content_href>&href__in=<blah1_href>,<blah2_href>,<blah3_href>
{
blah blah blah
}
</code></pre>
<p>Why not just encourage</p>
<pre><code>/repository/<uuid>/versions/?number__gte=5&content=<content_href>
</code></pre>
<p>An HREF is a glorified primary key, it seems silly to have the user be chucking those around unless they have nothing else to use, such as with ContentUnits (since the user-friendly names are attached to Artifacts, of which there can be many). That's the only model I can actually think of where it makes sense.</p> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=275462018-04-17T21:50:54Zdaviddavis
<ul></ul><p>I think the main use case is Katello. They store ids for objects and often times will want to look up lists of objects by their ids/hrefs. Since katello is a multi-tennant app, the names Katello is using for resources in Pulp are auto-generated so Katello uses ID to identify objects and often they are dealing with 100s or even 1000s of objects they want to get back. Filtering by ids/hrefs lets them submit a single request.</p>
<p>I'm not too concerned about getting this done anytime soon which is why it's post-MVP but we definitely will need this kind of filter I think. We can confirm with Katello about which specific objects they need to filter by ids/hrefs on.</p> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=427102019-04-26T20:36:56Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3</i></del>)</li></ul> Pulp - Story #3240: Add href_in_list as a filter for modelshttps://pulp.plan.io/issues/3240?journal_id=616542020-08-31T14:50:37Zdaviddavis
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - WONTFIX</i></li></ul>