You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/10/21 14:54:34 UTC

[jira] [Commented] (TIKA-1311) Centralize JSON handling of Metadata

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

Hudson commented on TIKA-1311:
------------------------------

SUCCESS: Integrated in tika-trunk-jdk1.7 #275 (See [https://builds.apache.org/job/tika-trunk-jdk1.7/275/])
clean up from TIKA-1311 (tallison: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1633357)
* /tika/trunk/tika-app/src/main/java/org/apache/tika/io


> Centralize JSON handling of Metadata
> ------------------------------------
>
>                 Key: TIKA-1311
>                 URL: https://issues.apache.org/jira/browse/TIKA-1311
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Minor
>             Fix For: 1.6
>
>         Attachments: TIKA-1311.patch
>
>
> When json was initially added to TIKA CLI (TIKA-213), there was a recommendation to centralize JSON handling of Metadata, potentially putting it in core.  On a recent bug fix (TIKA-1291), the same recommendation was repeated especially noting that we now handle JSON/Metadata differently in CLI and server.
> Let's centralize JSON handling in core and use GSON.  We should add a serializer and a deserializer so that users don't have to reinvent that wheel.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)