You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/08/16 21:08:01 UTC

[jira] [Commented] (NUTCH-2788) ParseData: improve presentation of Metadata in method toString()

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

Hudson commented on NUTCH-2788:
-------------------------------

SUCCESS: Integrated in Jenkins build Nutch » Nutch-trunk #3 (See [https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/3/])
NUTCH-2788 ParseData: improve presentation of Metadata in method toString() (snagel: [https://github.com/apache/nutch/commit/e8673d143446840e434506566f5362023ffaeca3])
* (edit) src/java/org/apache/nutch/parse/ParseData.java
* (edit) src/java/org/apache/nutch/parse/ParserChecker.java
* (edit) src/java/org/apache/nutch/metadata/Metadata.java


> ParseData: improve presentation of Metadata in method toString()
> ----------------------------------------------------------------
>
>                 Key: NUTCH-2788
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2788
>             Project: Nutch
>          Issue Type: Improvement
>          Components: metadata, parser
>    Affects Versions: 1.16
>            Reporter: Sebastian Nagel
>            Assignee: Sebastian Nagel
>            Priority: Minor
>             Fix For: 1.17
>
>
> See NUTCH-2567:
> bq. I would also suggest making the output of Metadata::toString more readable(for instance by adding a newline before each new metadata value). It would have made this bug way easier to spot inside the output of the parsechecker. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)