Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 1562 invoked from network); 29 May 2009 09:48:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 May 2009 09:48:10 -0000 Received: (qmail 12461 invoked by uid 500); 29 May 2009 09:48:22 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 12380 invoked by uid 500); 29 May 2009 09:48:22 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 12370 invoked by uid 99); 29 May 2009 09:48:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009 09:48:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pfmmaas@gmail.com designates 209.85.219.168 as permitted sender) Received: from [209.85.219.168] (HELO mail-ew0-f168.google.com) (209.85.219.168) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009 09:48:11 +0000 Received: by ewy12 with SMTP id 12so7124320ewy.11 for ; Fri, 29 May 2009 02:47:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer; bh=Nq3RKGvU+7298kjFXSXq/fX65u5rhGtJFN2ls2RfhOY=; b=wBRvf1Q6sA+e7MJxWMr0PDuJsaOZtOLsWGjnNxsCvadURWFAEn5wFI0cG9sqD7K081 E/3n+caq5eNZAb/9IdFyOs+4i7lzxVB5HPZufdYapndzER/1bqt/bIWABpijAiaSqxOD 3x48EQ0jhNDNFWTmLggMkODroM4RhpjUk54Zo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=x4w/bI1pL/pL7RMBNvQglbgnhD5S3j42rl8WkTKVdh/r3NQ7jDGlduEy6t2gmPsr17 cyqK+4ads2zX2On7iOvgweoEcr01Qd/MeGCUWXoGRbNGtRQifSL9YyaSwkXTOK4uRnzx GqvShSBE8llf1NYxEKkVbsE3gUoPoL5ISYKWg= Received: by 10.210.37.11 with SMTP id k11mr2199451ebk.62.1243590469245; Fri, 29 May 2009 02:47:49 -0700 (PDT) Received: from digi152.vpro.nl (digi152.vpro.nl [145.58.169.152]) by mx.google.com with ESMTPS id 5sm2209998eyf.38.2009.05.29.02.47.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 29 May 2009 02:47:48 -0700 (PDT) Message-Id: From: Peter Maas To: user@couchdb.apache.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Subject: handling keys in the REST view API Date: Fri, 29 May 2009 11:47:47 +0200 X-Mailer: Apple Mail (2.935.3) X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm trying to write a very basic fulltext search facility and managed to get something working: http://log4p.com/2009/05/28/simple-fulltext-analysis-in-couchdb/ Currently I sanitize the source text, remove stopwords (English that is) and emit a each term (with the number of occurences). Quite useful (for me) already. The next step would be to add stemming, not to hard either (have a working prototype already). This does however present me with a new problem. I'd like to stem the provided keys in the REST parameters using the same stemmer used by the mapping code. Is there a way to process the parameters passed to a REST view within CouchDB? Or would I need to duplicate (port) the stemmer in the clients (which are various in various languages)? kind regards, Peter