You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oodt.apache.org by "Brian Foster (JIRA)" <ji...@apache.org> on 2013/01/16 23:02:13 UTC

[jira] [Commented] (OODT-551) DataSourceCatalog implementation does not preserve order of metadata values

    [ https://issues.apache.org/jira/browse/OODT-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555508#comment-13555508 ] 

Brian Foster commented on OODT-551:
-----------------------------------

not sure why this is a problem since the key/values stored in this table are passed around in the code via a Metadata object which offers not such guarantees... why do you need the keys to be in an expected order?... can't you just do point lookups on the Metadata object?
                
> DataSourceCatalog implementation does not preserve order of metadata values
> ---------------------------------------------------------------------------
>
>                 Key: OODT-551
>                 URL: https://issues.apache.org/jira/browse/OODT-551
>             Project: OODT
>          Issue Type: Bug
>          Components: file manager
>    Affects Versions: 0.5
>            Reporter: Luca Cinquini
>            Assignee: Luca Cinquini
>             Fix For: 0.6
>
>
> The table that stores the metadata (key, value) pairs for the File Manager database-based implementation has no primary key - as a consequence, values are not guaranteed to be returned in any order, which is a problem for applications that rely on the order of the values (for example, among different metadata keys).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira