[ 
https://issues.apache.org/jira/browse/NUTCH-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085723#comment-13085723
 ] 

Markus Jelsma commented on NUTCH-1075:
--------------------------------------

I also see this on a clean 1.4-dev check out:

{code}
test:
     [echo] Testing plugin: protocol-file
    [junit] WARNING: multiple versions of ant detected in path for junit 
    [junit]          
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/Project.class
    [junit]      and 
jar:file:/home/markus/projects/apache/nutch/branch-1.4/build/lib/ant-1.6.5.jar!/org/apache/tools/ant/Project.class
    [junit] Running org.apache.nutch.protocol.file.TestProtocolFile
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.356 sec
    [junit] Running org.apache.nutch.analysis.lang.TestLanguageIdentifier
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
    [junit] Test org.apache.nutch.analysis.lang.TestLanguageIdentifier FAILED
    [junit] Running org.apache.nutch.analysis.lang.TestNGramProfile
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
    [junit] Test org.apache.nutch.analysis.lang.TestNGramProfile FAILED

{code}

> Delegate language identification to Tika
> ----------------------------------------
>
>                 Key: NUTCH-1075
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1075
>             Project: Nutch
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.4
>            Reporter: Julien Nioche
>            Assignee: Julien Nioche
>             Fix For: 1.4
>
>         Attachments: NUTCH-1075.patch
>
>
> In 2.0 the language identification is delegated to Tika and is done as part 
> of the parsing step (and not during the indexing as done currently).
> The patch attached is a backport from trunk which implements this and adds a 
> new parameter to determine the strategy to use
> {code:xml} 
> <property>
>   <name>lang.extraction.policy</name>
>   <value>detect,identify</value>
>   <description>This determines when the plugin uses detection and
>   statistical identification mechanisms. The order in which the
>   detect and identify are written will determine the extraction
>   policy. Default case (detect,identify)  means the plugin will
>   first try to extract language info from page headers and metadata,
>   if this is not successful it will try using tika language
>   identification. Possible values are:
>     detect
>     identify
>     detect,identify
>     identify,detect
>   </description>
> </property>
> {code} 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to