You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tika.apache.org by Stephen H <st...@jiglu.com> on 2022/04/26 10:51:00 UTC
ForkParser issues with 2.3.0
Hi,
I'm currently in the process of moving a system over to use ForkParser
with Tika 2.3.0 but there's some issues I'm having.
First, I'd hoped to use the 'ForkParser(Path tikaBin,
ParserFactoryFactory factoryFactory)' constructor to get better
isolation, but have run into the issue described in TIKA-3223 where it
can't find an exception class, for example if parsing an encrypted
document. For now I've switched to using a 'legacy' constructor but it
would be nice to eventually move to the newer method.
Second, there seems to be some work missing in the handling of metadata
from certain parsers when using ForkParser. For example, for
OpenDocument ODP and ODS files and Microsoft Open XML formats, while the
document text is returned there is no metadata in either the returned
Metadata object or in the returned HTML head. The OpenDocument ODT
format works as expected via ForkParser though.
For an audio/mp4 file, the title is returned but the rest of the
metadata is missing, although the values are present in the body of the
returned HTML. For an video/mp4 file, metadata values are only present
in the body of the HTML and in the Metadata object it has an incorrect
video/quicktime content type.
If it's possible to squeeze fixing this second issue into the next
version it would be really helpful!
Thanks,
Stephen.
Re: ForkParser issues with 2.3.0
Posted by Nick Burch <ap...@gagravarr.org>.
On Tue, 26 Apr 2022, Stephen H wrote:
> On 26/04/2022 12:22, Nick Burch wrote:
>> Are you able to write a short junit unit test case which shows this issue?
>> We have a bunch of small test OOXML and ODF files that could be used
>
> I've done this - if I create an issue in Jira with it would that best?
Yup!
> There isn't currently an ODS file in the parsers test set with a title though
> there is one with a creator, which is enough to show the issue. I also
> couldn't see an MP4 video file that had any metadata in it.
If you have / could create a tiny MP4 file with some metadata, that'd be
great!
Not sure if it's enough to trigger the OpenDocument bug, but there's a
title in this test file:
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-miscoffice-module/src/test/resources/test-document/testOpenOffice2.odf
Nick
Re: ForkParser issues with 2.3.0
Posted by Stephen H <st...@jiglu.com>.
On 26/04/2022 12:22, Nick Burch wrote:
> Are you able to write a short junit unit test case which shows this
> issue? We have a bunch of small test OOXML and ODF files that could be used
I've done this - if I create an issue in Jira with it would that best?
There isn't currently an ODS file in the parsers test set with a title
though there is one with a creator, which is enough to show the issue. I
also couldn't see an MP4 video file that had any metadata in it.
Cheers,
Stephen.
Re: ForkParser issues with 2.3.0
Posted by Nick Burch <ap...@gagravarr.org>.
On Tue, 26 Apr 2022, Stephen H wrote:
> Second, there seems to be some work missing in the handling of metadata
> from certain parsers when using ForkParser. For example, for
> OpenDocument ODP and ODS files and Microsoft Open XML formats, while the
> document text is returned there is no metadata in either the returned
> Metadata object or in the returned HTML head. The OpenDocument ODT
> format works as expected via ForkParser though.
Are you able to write a short junit unit test case which shows this issue?
We have a bunch of small test OOXML and ODF files that could be used
Nick