Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 44942 invoked from network); 6 Dec 2010 14:38:39 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Dec 2010 14:38:39 -0000 Received: (qmail 35003 invoked by uid 500); 6 Dec 2010 14:38:38 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 34892 invoked by uid 500); 6 Dec 2010 14:38:37 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 34571 invoked by uid 99); 6 Dec 2010 14:38:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Dec 2010 14:38:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Dec 2010 14:38:34 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB6EcDpn028892 for ; Mon, 6 Dec 2010 14:38:13 GMT Message-ID: <25829816.128751291646292976.JavaMail.jira@thor> Date: Mon, 6 Dec 2010 09:38:12 -0500 (EST) From: "Robert Muir (JIRA)" To: dev@lucene.apache.org Subject: [jira] Commented: (SOLR-1979) Create LanguageIdentifierUpdateProcessor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/SOLR-1979?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12967= 201#action_12967201 ]=20 Robert Muir commented on SOLR-1979: ----------------------------------- bq. Both also rely on those fields existing. I don't think this check should be at "runtime" either. What if you are indexing lots of documents and suddenly you encounter a tha= i document (or mis-detected as Thai!) and the whole thing fails? Can't we validate the output mapping (and log it!) at initialization time? > Create LanguageIdentifierUpdateProcessor > ---------------------------------------- > > Key: SOLR-1979 > URL: https://issues.apache.org/jira/browse/SOLR-1979 > Project: Solr > Issue Type: New Feature > Components: update > Reporter: Jan H=C3=B8ydahl > Assignee: Grant Ingersoll > Priority: Minor > Attachments: SOLR-1979.patch, SOLR-1979.patch, SOLR-1979.patch > > > We need the ability to detect language of some random text in order to ac= t upon it, such as indexing the content into language aware fields. Another= usecase is to be able to filter/facet on language on random unstructured c= ontent. > To do this, we wrap the Tika LanguageIdentifier in an UpdateProcessor. Th= e processor is configurable like this: > {code:xml}=20 > > name,subject > language_s > id > en > > {code}=20 > It will then read the text from inputFields name and subject, perform lan= guage identification and output the ISO code for the detected language in t= he outputField. If no language was detected, fallback language is used. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org