[ http://issues.apache.org/jira/browse/NUTCH-290?page=comments#action_12413637 ]
Stefan Neufeind commented on NUTCH-290: --------------------------------------- this one here fires in the PDF-parser: } catch (Exception e) { // run time exception LOG.warning("General exception in PDF parser: "+e.getMessage()); e.printStackTrace(); return new ParseStatus(ParseStatus.FAILED, "Can't be handled as pdf document. " + e).getEmptyParse(getConf()); } The exception is: 060522 001010 General exception in PDF parser: You do not have permission to extract text java.io.IOException: You do not have permission to extract text at org.pdfbox.util.PDFTextStripper.writeText(PDFTextStripper.java:189) at org.pdfbox.util.PDFTextStripper.getText(PDFTextStripper.java:140) at org.apache.nutch.parse.pdf.PdfParser.getParse(PdfParser.java:120) at org.apache.nutch.parse.ParseUtil.parse(ParseUtil.java:77) at org.apache.nutch.fetcher.Fetcher$FetcherThread.output(Fetcher.java:257) at org.apache.nutch.fetcher.Fetcher$FetcherThread.run(Fetcher.java:143) Could it be that, maybe as a fallback, in case the document can't be parsed and no "description" is returned that in search-output the document itself is used as "description"? If yes: In case of binary files this seems to lead to problems. > parse-pdf: Garbage (?) indexed when text-extraction now allowed > --------------------------------------------------------------- > > Key: NUTCH-290 > URL: http://issues.apache.org/jira/browse/NUTCH-290 > Project: Nutch > Type: Bug > Components: indexer > Versions: 0.8-dev > Reporter: Stefan Neufeind > > It seems that garbage (or undecoded text?) is indexed when text-extraction > for a PDF is not allowed. > Example-PDF: > http://www.task-switch.nl/Dutch/articles/Management_en_Architectuur_v3.pdf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira