[
https://issues.apache.org/jira/browse/OODT-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559521#comment-13559521
]
Brian Foster edited comment on OODT-551 at 1/22/13 9:53 AM:
------------------------------------------------------------
got it!!!... if we are not caring about the add order of the keys, i'm a total
+1... and i see how this is really a bug now... a key's values for Metadata are
store as List<String> and even Metadata's method signatures use this, so each
key's value order should be maintained since a Java List is an "ordered"
Collection... +1!!
was (Author: bfoster):
got it!!... if we are not caring about the add order of the keys, i'm a
total +1... and i see how this is really a bug now... a key's values for
Metadata are store as List<String> and even Metadata's method signatures use
this, so each key's value order should be maintained since a Java List is an
"ordered" Collection... +1!!
> 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
>
> Attachments: OODT-551.luca.patch.txt
>
>
> 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
