https://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232018-02-28T08:52:02ZNDN project issue tracking systemrepo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=225282018-02-28T08:52:02Zweijia yuan
<ul><li><strong>Assignee</strong> changed from <i>Alex Afanasyev</i> to <i>weijia yuan</i></li></ul> repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=226422018-03-06T16:10:53ZJunxiao Shi
<ul></ul><p>This should wait for <a class="issue tracker-2 status-5 priority-2 priority-default closed" title="Feature: Decode v0.3 Interest format and interpret as v0.2 (Closed)" href="https://redmine.named-data.net/issues/4527">#4527</a>, because repo-ng needs to handle CanBePrefix flag. Otherwise, it would be difficult to re-add it.</p>
repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=226742018-03-14T03:57:17ZJunxiao Shi
<ul></ul><blockquote>
<p>Is there a specific reason that names are stored as blob type?</p>
</blockquote>
<p>Yes. Names are binary, always. They should be processed and stored as such.</p>
<blockquote>
<p>It's not easy to do name prefix matching using blob. If we store name as string in the database, then it will be easy to implement prefix matching.</p>
</blockquote>
<p>In SQL there’s no “prefix matching”. Instead, you convert the query to “WHERE name >= query AND name < successor-of(query)”.<br>
See example in repo-sql: <a href="https://github.com/3rd-ndn-hackathon/repo-sql/blob/47671612ef8b7c40931e5129c4d82626033f90a1/src/query-processor.cpp#L98-L99">https://github.com/3rd-ndn-hackathon/repo-sql/blob/47671612ef8b7c40931e5129c4d82626033f90a1/src/query-processor.cpp#L98-L99</a></p>
repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=226752018-03-14T06:27:22ZAlex Afanasyev
<ul></ul><p>Junxiao, I think there is a problem with this logic. As far as I understand, it would work if we exclude T and L for the overall name in the stored value, but should have undefined results when comparing name as a whole. Am I misremembering our previous discussion of <a href="http://named-data.net/doc/NDN-packet-spec/current/name.html#canonical-order">http://named-data.net/doc/NDN-packet-spec/current/name.html#canonical-order</a> ?</p>
repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=229052018-04-06T10:30:14ZJunxiao Shi
<ul></ul><blockquote>
<p>it would work if we exclude T and L for the overall name in the stored value</p>
</blockquote>
<p>Yes, the <code>name</code> column should only store NAME-VALUE.<br>
<a href="https://github.com/3rd-ndn-hackathon/repo-sql/blob/91eb215e90dd66e0711f3a8d705ef4b788c7a4d7/src/database-conn.cpp#L90">https://github.com/3rd-ndn-hackathon/repo-sql/blob/91eb215e90dd66e0711f3a8d705ef4b788c7a4d7/src/database-conn.cpp#L90</a><br>
<a href="https://github.com/3rd-ndn-hackathon/repo-sql/blob/91eb215e90dd66e0711f3a8d705ef4b788c7a4d7/src/database-conn.cpp#L21">https://github.com/3rd-ndn-hackathon/repo-sql/blob/91eb215e90dd66e0711f3a8d705ef4b788c7a4d7/src/database-conn.cpp#L21</a></p>
repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=236262018-07-13T10:26:05ZJunxiao Shi
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-3 status-5 priority-2 priority-default closed" href="/issues/4456">Task #4456</a>: clean up the existing repo-ng code</i> added</li></ul> repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=241082018-10-01T00:00:49Zweijia yuan
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-3 status-1 priority-2 priority-default" href="/issues/4523">Task #4523</a>: Add Sync support for repo</i> added</li></ul> repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=245272019-01-10T15:38:05ZDavide Pesavento
<ul><li><strong>Subject</strong> changed from <i>Remove selector from old interest format</i> to <i>Remove selectors from old interest format</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/24527/diff?detail_id=21584">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>Is this done? if not, what's missing?</p>
repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=245282019-01-10T15:40:42Zweijia yuan
<ul></ul><p>Yes this is finished and merged.</p>
repo-ng - Task #4522: Remove selectors from old interest formathttps://redmine.named-data.net/issues/4522?journal_id=245332019-01-13T13:57:09ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul>