[
https://issues.apache.org/jira/browse/TIKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480137#comment-17480137
]
Tim Allison edited comment on TIKA-3657 at 1/21/22, 3:33 PM:
-------------------------------------------------------------
I've created a simple project here:
[https://github.com/tballison/tika-addons/tree/main/tika-app-custom-docker]
I'm able to reproduce this with testWORD_embedded_pdf.doc. I get the embedded
PDF with straight tika-app.jar but not in Docker with this config file.
The custom tika-config.xml has no effect. If I back off to an empty
tika-config or the default, the embedded file is processed the same.
As [~comcortim] pointed out, everything works as long as we don't set an
EmbeddedDocumentExtractor in the parseContext. If I set a
PDFParserConfig.class, though, it looks like it is working...so I'm not able to
replicate "set anything in the parseContext".
was (Author: [email protected]):
I've created a simple project here:
[https://github.com/tballison/tika-addons/tree/main/tika-app-custom-docker]
I'm able to reproduce this with testWORD_embedded_pdf.doc. I get the embedded
PDF with straight tika-app.jar but not in Docker with this config file.
> Microsoft documents are not text parsed when running under Docker
> -----------------------------------------------------------------
>
> Key: TIKA-3657
> URL: https://issues.apache.org/jira/browse/TIKA-3657
> Project: Tika
> Issue Type: Bug
> Components: config, core, depedency
> Affects Versions: 2.2.0, 2.2.1
> Reporter: Tim Barrett
> Priority: Major
> Fix For: 2.2.2
>
> Attachments: tika-config.xml
>
>
> We use EmbeddedDocumentExtractor, with this code:
> NalyticsEmbeddedDocumentExtractor nalyticsEmbeddedDocumentExtractor = *new*
> NalyticsEmbeddedDocumentExtractor(*this*);
> *this*.context.set(EmbeddedDocumentExtractor.*class*,
> nalyticsEmbeddedDocumentExtractor);
> This all works fine for us, and has been used in production for a few years.
> This also works under Tika 2.2.0 when running in development environments
> (Eclipse, Apache Tomcat). However when running under Docker the text
> withinMicrosoft documents (Word etc) is not parsed. Under Tika 2.1.0, under
> Docker, the Microsoft documents are fully parsed, so this problem was
> introduced in 2.2.0
> Interestingly, I found that if *anything at all* is added to the context via
> context.set the same problem occurs. Also, if the standard Tika Embedded
> Document Extractor is used the same problem occurs. Our Docker image contains
> our application's code which uses Tika, as well as Apache DS. The problem
> occurs running Docker on Ubuntu, Mac OS and Windows.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
