oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OODT-529) Lenient Lucene Catalog
Date Thu, 01 Nov 2012 23:30:12 GMT

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

Chris A. Mattmann commented on OODT-529:
----------------------------------------

This property would be read by the LuceneCatalogFactory and passed as a constructor arg to
the LuceneCatalog (adding a new constructor that took this field, preserving the existing
constructor with an internal default value of false set), added to the default filemgr.properties
with a default value of false (and a documentation comment above it), and then if not found
in the LuceneCatalogFactory on lookup, would be set to false by default. 
                
> Lenient Lucene Catalog
> ----------------------
>
>                 Key: OODT-529
>                 URL: https://issues.apache.org/jira/browse/OODT-529
>             Project: OODT
>          Issue Type: Improvement
>          Components: file manager
>    Affects Versions: 0.4
>            Reporter: Luca Cinquini
>            Assignee: Luca Cinquini
>             Fix For: 0.5
>
>
> There is often a need for ingesting and using metadata fields that are dynamically named,
rather than being exactly defined in an XML schema used by the CAS Validation Layer.
> We should either expand the current LuceneCatalog implementation to allow arbitrary fields,
or provide an alternative implementation that does so.

--
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

Mime
View raw message