[
https://issues.apache.org/jira/browse/OODT-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558414#comment-13558414
]
Chris A. Mattmann commented on OODT-551:
----------------------------------------
Oh sorry forgot to mention I'm also proposing to do this in a back compat way
for DataSourceCatalog. By default it will still return unordered values,
respecting Metadata's belief in the same. With a property flag turned on, the
deployer of the OODT FM and configurer of the FM DataSourceCatalog can turn on
metadata value ordering for his or her instance, and only in the case of the FM
Catalog (so querying from it). That's it.
> 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
