tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Gauss II (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1027) Allow null values when setting metadata
Date Mon, 19 Nov 2012 15:28:58 GMT

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

Ray Gauss II commented on TIKA-1027:
------------------------------------

We'll want to define suggested behavior for embedding since a {{Metadata}} object is passed
to an embedder containing the values to be set, and in some cases users will want to set certain
fields to {{null}}.

An empty String could be used to indicate that a particular field should be set to {{null}}
by the embedder, but if we move to something other than Strings to hold values in the {{Metadata}}
class we'll need to re-evaluate.
                
> Allow null values when setting metadata
> ---------------------------------------
>
>                 Key: TIKA-1027
>                 URL: https://issues.apache.org/jira/browse/TIKA-1027
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.3
>
>
> Many file formats have optional metadata entries that result in a lot of {{if (value
== null)}} statements around {{metadata.set(...)}} calls. It would be more convenient if the
{{set}} method explicitly allowed a {{null}} value and that a call like {{metadata.set(name,
null)}} was essentially equivalent to a {{metadata.remove(name)}} call.

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