[jira] [Commented] (TIKA-2349) Try to match digests when finding equivalent embedded files in tika-eval Compare

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on TIKA-2349:
------------------------------

UNSTABLE: Integrated in Jenkins build tika-2.x #248 (See [https://builds.apache.org/job/tika-2.x/248/])
TIKA-2349 -- try to match embedded docs by digest in tika-eval "Compare" (tallison: rev c67e6223650eb8f157865293679e6f3af920b826)
* (add) tika-eval/src/test/resources/test-dirs/extractsB/file14_diffAttachOrder.json
* (add) tika-eval/src/test/resources/test-dirs/extractsA/file14_diffAttachOrder.json
* (edit) tika-eval/src/test/java/org/apache/tika/eval/SimpleComparerTest.java
* (edit) tika-eval/src/main/java/org/apache/tika/eval/ExtractComparer.java


> Try to match digests when finding equivalent embedded files in tika-eval Compare
> --------------------------------------------------------------------------------
>
>                 Key: TIKA-2349
>                 URL: https://issues.apache.org/jira/browse/TIKA-2349
>             Project: Tika
>          Issue Type: Improvement
>          Components: tika-eval
>            Reporter: Tim Allison
>            Priority: Trivial
>             Fix For: 2.0, 1.15
>
>
> In tika-eval {{Compare}}, there's some code that tries to find equivalent embedded files.  The challenge is that embedded resource paths may contain different names in different versions of Tika, or they may be at different offsets within the {{List<Metadata>}}.  In the most recent regression run, we had several cases where the {{List<Metadata>}}s were the same size, but the attachments were ordered differently.
> Instead of relying solely on position, let's try to match digest keys first, then back off to path names, and finally, back off equal locations in the list, if the lists have the same size.
> More areas for improvement will exist for this bit of code...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)