[
https://issues.apache.org/jira/browse/TIKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487009#comment-17487009
]
Tim Allison commented on TIKA-3657:
-----------------------------------
>Re the markLimit - although there are ways of dealing with this via the config
>(which is now working) or indeed via spoolToDisk, I still think that having a
>hard value set in the POIFSDetector is the simplest way to go, considering
>that email files out in the wild are often > 16MB in size.
I bumped this yesterday (https://issues.apache.org/jira/browse/TIKA-3672).
Will not make it into 2.3.0 unless we have to respin release candidate #1, but
will be in next release.
> I have no idea, that was a mystery to me too and I'd still like to get to the
> bottom of it
I'll take a look today. If I don't find anything obvious, y, let's meet some
time next week.
> 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
> Attachments: POIFSContainerDetector.java, scenario traces.txt,
> 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)
