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

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

Indeed, it does. However, i seem to be unable to retrieve the language anymore. 
All output is without the lang field. The plugin is enabled as 
language-identifier and compiled:

{code}
bin/nutch parsechecker -D lang.extraction.policy=identify http://www.groene.nl
{code}

{code}
Content Metadata: X-Runtime=46 ETag="0305dcdfd8a9f88f049403af666c8f29" 
Content-Length=7692 
Set-Cookie=_groene.nl_session=BAh7CDoQX2NzcmZfdG9rZW4iMTREczFGMnZaV3g2ejBJNGI3QllNZDFlRWFBTTZlbEw0VGFXS2VEMGdNS289Og9zZXNzaW9uX2lkIiU1YTZjYzNhNjQwNDY0ZjE0NGIzMjA4OTgyNGUwYTFlMDoPaG9tZV92aWV3c2kA--d4aa63ef6783ae64e1ba09c92ba0c95297adf803;
 path=/; HttpOnly Connection=close Server=Apache X-Powered-By=Phusion Passenger 
(mod_rails/mod_rack) 2.2.14 Cache-Control=private, max-age=0, must-revalidate 
Status=200 Date=Tue, 16 Aug 2011 13:26:13 GMT Vary=Accept-Encoding 
Content-Encoding=gzip h1=null Content-Type=text/html; charset=utf-8 h2=klaver 
Parse Metadata: robots=noarchive caching.forbidden=content 
Content-Encoding=UTF-8 Content-Type=text/html; charset=utf-8 
{code}

Haven't got a clue yet. I also doesn't matter if i disable the boilerplate 
patches.

> 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