You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2017/11/16 16:16:00 UTC
[jira] [Commented] (NUTCH-2457) Embedded documents likely not
correctly parsed by Tika
[ https://issues.apache.org/jira/browse/NUTCH-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255540#comment-16255540 ]
Tim Allison commented on NUTCH-2457:
------------------------------------
I'm sure this is user error, and I need to put something else on my path, but I'm still getting this:
{noformat}
java.lang.RuntimeException: x-point org.apache.nutch.protocol.Protocol not found.
at org.apache.nutch.protocol.ProtocolFactory.<init>(ProtocolFactory.java:53)
at org.apache.nutch.tika.TestMSWordParser.getTextContent(TestMSWordParser.java:66)
{noformat}
> Embedded documents likely not correctly parsed by Tika
> ------------------------------------------------------
>
> Key: NUTCH-2457
> URL: https://issues.apache.org/jira/browse/NUTCH-2457
> Project: Nutch
> Issue Type: Bug
> Reporter: Tim Allison
>
> While working on TIKA-2490, I think I found that Nutch's current method of requesting a mime-specific parser for each file will fail to parse embedded files, e.g. https://github.com/apache/tika/blob/master/tika-server/src/test/resources/test_recursive_embedded.docx
> The fix should be straightforward, and I'll submit a PR once I can get Nutch up and running in my dev environment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)