Sounds like that could get interesting if the metadata had to deal with values that are part of a time series - such as versions of files created on different dates or identifying files that are similar except for the time interval of the data they contain.
Bruce B. On Thu, Jan 17, 2013 at 9:52 AM, Luca Cinquini (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/OODT-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556230#comment-13556230] > > Luca Cinquini commented on OODT-551: > ------------------------------------ > > Having a flag sounds good to me. I can have that done by the end of the > week, unless you have it already. > And I will fix the unit test, sorry about that. > > > 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 >
