Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 582ED17EBE for ; Thu, 1 Oct 2015 16:51:11 +0000 (UTC) Received: (qmail 18746 invoked by uid 500); 1 Oct 2015 16:51:07 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 18686 invoked by uid 500); 1 Oct 2015 16:51:07 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 18674 invoked by uid 99); 1 Oct 2015 16:51:06 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2015 16:51:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 362B1C81A0 for ; Thu, 1 Oct 2015 16:51:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.12 X-Spam-Level: X-Spam-Status: No, score=-0.12 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ro-T8iX5pq91 for ; Thu, 1 Oct 2015 16:50:57 +0000 (UTC) Received: from mail-yk0-f181.google.com (mail-yk0-f181.google.com [209.85.160.181]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 05A9342AB6 for ; Thu, 1 Oct 2015 16:50:57 +0000 (UTC) Received: by ykdg206 with SMTP id g206so83890852ykd.1 for ; Thu, 01 Oct 2015 09:50:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=J91EmNt7qeigGzTub35GWthFFBgJpIVhv7BC8jpmyu0=; b=myALfzxh7v9rd7ljkqdRc0Rp7ukRyDOQwByzVZQw6FcWgCBglhhh6NdxDyRa/PGMo8 vWD7A3yOGIsAllK3gYCuXscD56W5mPKOHanu9ofHA7rKkC+AJMc0gwPHnBVfeMW74Qj+ j/4euE/5QYl228UzKST0YOYB5oT2ML2OPyO1H2NYqsMGiygklXZoSx5y8EuJwFuj4shA BXucu+8cYZKJb3lF1oiWe/COLXTz5bOxG8aiyL3xzxhNeIvKIaGx3FdXpgHeFina5w6O 7+xw8t9c1Ix4dI8Htx5YeRPxfil46Xf373d7Eks96C45FbwrgZTZ274JzEM9iXTKGN7F xpAw== X-Received: by 10.170.222.212 with SMTP id o203mr9113077ykf.73.1443718256662; Thu, 01 Oct 2015 09:50:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.87.68 with HTTP; Thu, 1 Oct 2015 09:50:17 -0700 (PDT) In-Reply-To: <560D6185.7080406@noaa.gov> References: <560D1D7D.2070805@noaa.gov> <560D6185.7080406@noaa.gov> From: Alexandre Rafalovitch Date: Thu, 1 Oct 2015 12:50:17 -0400 Message-ID: Subject: Re: Solr vs Lucene To: solr-user Content-Type: text/plain; charset=UTF-8 Is that with Lucene or with Solr? Because Solr has several different spell-checker modules you can configure. I would recommend trying them first. And, frankly, I still don't know what your business case is. Regards, Alex. ---- Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start.com/ On 1 October 2015 at 12:38, Mark Fenbers wrote: > Yes, and I've spend numerous hours configuring and reconfiguring, and > eventually even starting over, but still have not getting it to work right. > Even now, I'm getting bizarre results. For example, I query "NOTE: This > is purely as an example." and I get back really bizarre suggestions, like > "n ot e" and "n o te" and "n o t e" for the first word which isn't even > misspelled! The same goes for "purely" and "example" also! Moreover, I get > extended results showing the frequencies of these suggestions being over > 2600 occurrences, when I'm not even using an indexed spell checker. I'm > only using a file-based spell checker (/usr/shar/dict/words), and the > wordbreak checker. > > At this point, I can't even figure out how to narrow down my confusion so > that I can post concise questions to the group. But I'll get there > eventually, starting with removing the wordbreak checker for the time-being. > Your response was encouraging, at least. > > Mark > > > > On 10/1/2015 9:45 AM, Alexandre Rafalovitch wrote: >> >> Hi Mark, >> >> Have you gone through a Solr tutorial yet? If/when you do, you will >> see you don't need to code any of this. It is configured as part of >> the web-facing total offering which are tweaked by XML configuration >> files (or REST API calls). And most of the standard pipelines are >> already pre-configured, so you don't need to invent them from scratch. >> >> On your specific question, it would be better to ask what _business_ >> level functionality you are trying to achieve and see if Solr can help >> with that. Starting from Lucene code is less useful :-) >> >> Regards, >> Alex. >> ---- >> Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: >> http://www.solr-start.com/ >> >> >> On 1 October 2015 at 07:48, Mark Fenbers wrote: