[
https://issues.apache.org/jira/browse/NUTCH-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132637#comment-17132637
]
Hudson commented on NUTCH-2788:
-------------------------------
SUCCESS: Integrated in Jenkins build Nutch-trunk #3685 (See
[https://builds.apache.org/job/Nutch-trunk/3685/])
NUTCH-2788 ParseData: improve presentation of Metadata in method (snagel:
[https://github.com/apache/nutch/commit/e3f7725dace31acb2455bce5c6950ec5ee28ec18])
* (edit) src/java/org/apache/nutch/metadata/Metadata.java
* (edit) src/java/org/apache/nutch/parse/ParserChecker.java
* (edit) src/java/org/apache/nutch/parse/ParseData.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)
