https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422016-07-26T13:41:29ZArvadosArvados - Feature #9665: Arvados' PostgreSQL jsonb supporthttps://dev.arvados.org/issues/9665?journal_id=413962016-07-26T13:41:29ZBrett Smithbrett.smith@curii.com
<ul></ul><p>Alexander,</p>
<p>Upgrading PostgreSQL, by itself, won't mean these attributes start using jsonb columns for <code>properties</code> and other serialized fields. The serialization is handled by Rails itself. In order to switch these columns to jsonb, we'd have to upgrade API server's Rails version; possibly upgrade to a PostgreSQL database adapter that supports the jsonb column type; start using that as our column serialization type in the API server code; and require all users to upgrade to PostgreSQL 9.3+.</p>
<p>Does that answer your question?</p> Arvados - Feature #9665: Arvados' PostgreSQL jsonb supporthttps://dev.arvados.org/issues/9665?journal_id=414442016-07-27T12:03:57ZAlexander Afanasyevaafanasyev@parseq.pro
<ul></ul><p>Brett,</p>
<p>Yes, I know. Actually, the question was whether you are going to do any of such "cumulative" upgrade (I'm sorry for my inaccurate characterization)?</p>
<p>The reason why I'm asking, that this is <em>the way you are storing</em> (json) properties in the database, so to work with properties in a more "intellectual way" (for example, filtering by some properties key's value), we need to tie this process <em>to this realization</em>. And on the other hand, presenting such data structure in the database, probably, will allow to tackle such things in a more natural way (about of the box). So I just wondered whether this would be changed in the future or not.</p> Arvados - Feature #9665: Arvados' PostgreSQL jsonb supporthttps://dev.arvados.org/issues/9665?journal_id=414452016-07-27T13:17:21ZBrett Smithbrett.smith@curii.com
<ul></ul><p>Alexander Afanasyev wrote:</p>
<blockquote>
<p>Yes, I know. Actually, the question was whether you are going to do any of such "cumulative" upgrade (I'm sorry for my inaccurate characterization)?</p>
</blockquote>
<p>Alexander,</p>
<p>I apologize that I misunderstood. Yes, we have discussed doing exactly this upgrade, to provide exactly the kinds of features you're talking about. That's in issue <a class="issue tracker-6 status-3 priority-4 priority-default closed parent" title="Idea: [API] Support query of "properties" field on objects (Resolved)" href="https://dev.arvados.org/issues/4019">#4019</a>, which describes the same upgrade path you suggested. Would it be OK if I closed this ticket as a duplicate of that one?</p> Arvados - Feature #9665: Arvados' PostgreSQL jsonb supporthttps://dev.arvados.org/issues/9665?journal_id=414482016-07-27T13:37:39ZAlexander Afanasyevaafanasyev@parseq.pro
<ul></ul><p>Yes, of cause!</p>
<p>Thanks, Brett.</p> Arvados - Feature #9665: Arvados' PostgreSQL jsonb supporthttps://dev.arvados.org/issues/9665?journal_id=414492016-07-27T13:53:01ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Duplicate</i></li></ul>