[
https://issues.apache.org/jira/browse/TIKA-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721439#comment-17721439
]
Hudson commented on TIKA-4033:
------------------------------
FAILURE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #1079 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/1079/])
TIKA-4033 -- improve metadata handling for incremental updates. Generalize
incremental updates to "version" and avoid use of synthetic name for
resourceName. (#1121) (github:
[https://github.com/apache/tika/commit/f30180baa6b7da6ad56ff1e4f5f963d0fc7f4e84])
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/src/test/java/org/apache/tika/parser/pdf/PDFIncrementalUpdatesTest.java
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/java/org/apache/tika/parser/pdf/PDFParserTest.java
* (edit)
tika-core/src/main/java/org/apache/tika/metadata/TikaCoreProperties.java
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/src/main/java/org/apache/tika/parser/pdf/PDFParser.java
* (edit)
tika-core/src/main/java/org/apache/tika/parser/RecursiveParserWrapper.java
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/src/main/java/org/apache/tika/parser/pdf/AbstractPDF2XHTML.java
* (edit) tika-core/src/main/java/org/apache/tika/metadata/PDF.java
> Improve metadata for incremental updates, take 2
> ------------------------------------------------
>
> Key: TIKA-4033
> URL: https://issues.apache.org/jira/browse/TIKA-4033
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Trivial
> Fix For: 2.8.0
>
>
> We're currently generating a "resourceName" in the PDFParser for incremental
> updates. The following isn't well documented (I don't think?), but we try to
> reserve "resourceName" for embedded files to be the actual name that the
> container document has for that embedded file.
> Now, we need some kind of name for the embedded resource path in
> RecursiveParserWrapper, so we generate something based on the resourceName
> or, if that doesn't exist, the the relationship id, and if that doesn't exist
> we create /embedded-NUM.
> But that's a separate issue.
> We should use another option so that RecursiveParserWrapper knows to name the
> path /version-number-0 or similar. We should not misuse "resourceName".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
