You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nick Burch (JIRA)" <ji...@apache.org> on 2012/05/16 23:45:06 UTC

[jira] [Resolved] (TIKA-927) Composite Properties

     [ https://issues.apache.org/jira/browse/TIKA-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Burch resolved TIKA-927.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 1.2
    
> Composite Properties
> --------------------
>
>                 Key: TIKA-927
>                 URL: https://issues.apache.org/jira/browse/TIKA-927
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 1.1
>            Reporter: Ray Gauss II
>             Fix For: 1.2
>
>         Attachments: tika-composite-properties-core.diff
>
>
> A composite property type would be useful for maintaining backwards compatibility when migrating old properties or aliasing a single primary property to several secondary fields.
> To achieve this the Property class could allow for defining a composite type which aliases a primary Property and an optional list of secondaryExtractProperties which can be used to set additional metadata properties with the same value as the primary.
> The name of the composite property would be taken from its primary property.
> The primary and secondary children of a composite property must not be composite properties themselves or a PropertyTypeException will be thrown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira