Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 99397ECA0 for ; Wed, 5 Dec 2012 14:17:46 +0000 (UTC) Received: (qmail 44255 invoked by uid 500); 5 Dec 2012 14:17:46 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 44174 invoked by uid 500); 5 Dec 2012 14:17:45 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 44160 invoked by uid 99); 5 Dec 2012 14:17:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 14:17:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gary.martin@wandisco.com designates 209.85.217.175 as permitted sender) Received: from [209.85.217.175] (HELO mail-lb0-f175.google.com) (209.85.217.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 14:17:36 +0000 Received: by mail-lb0-f175.google.com with SMTP id gg13so3992732lbb.6 for ; Wed, 05 Dec 2012 06:17:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=r4Ll2XAoMzoODvQyCGzvPpdsMeRSMw6Oz4W95CjNFfU=; b=PCD8WeS2dFHl1ugHVPMMkBfxabgLGdUuJ+rE7KMZxunySGpcYjjL+AIyJ8iIMJxp9U 3mf4gLQefbNMYHu2vLMmUMxMw/w5OVdgkVNxJ3Ce3wmq4tNY6LrHM9FAG4HRufUVVheh 2cwbMUT2YuPUWx2BVo6bWlRRDJwJW67kSQJKPVgtwj5AGYLuZN8ed+D8K3ormnfFyZVW ZvVdM8/PlU410/d+Ehnu++28zt6alu5L2NSDkTx9v80ZqKDt+To5AxnECZ2Dlknrm7Ih VmcTEBYOQhOlq31n7kme3M9H1oLAAHmPKPB1zjJktG8NozlMsUytb6O25nYA6sXhxbP7 MRPA== Received: by 10.112.82.166 with SMTP id j6mr7509753lby.25.1354717034065; Wed, 05 Dec 2012 06:17:14 -0800 (PST) Received: from [10.2.5.205] ([77.86.30.139]) by mx.google.com with ESMTPS id pw17sm2162575lab.5.2012.12.05.06.17.11 (version=SSLv3 cipher=OTHER); Wed, 05 Dec 2012 06:17:12 -0800 (PST) Message-ID: <50BF575E.1040307@wandisco.com> Date: Wed, 05 Dec 2012 14:17:02 +0000 From: Gary Martin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: bloodhound-dev@incubator.apache.org Subject: Re: [Apache Bloodhound] Proposals/BEP-0004/ResourceQuery added References: <20121128151735.03AEB803AF@bloodhound-vm> <50BE0908.7090900@wandisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQl8RS7QGekWjw33fcI8a25ky47mIZpzQy/kTfAzPyCVPNVDevCN76ba7STDuCAW8WIfW+GD X-Virus-Checked: Checked by ClamAV on apache.org On 05/12/12 13:43, Andrej Golcov wrote: > Hi, > >> It does worry me that it might not be the best idea to support lucene as >> well as existing syntax but if there are existing parsers for the lucene >> style syntax it may be OK. Perhaps there is a way of using Whoosh to >> provide parsing services for us. > Do you mean to use Whoosh query parser to parse Bloodhound Search query? > That will bring us a lot functionality with much less effort and bugs. > From the first look, Whoosh query syntax > (http://packages.python.org/Whoosh/querylang.html) covers at least 90% > of our requirements. According to Whoosh code, it can be also > extended: http://packages.python.org/Whoosh/parsing.html. In case of > PyLucene usage, we will provide query mapping from Whoosh to Lucen. > > There are few drawbacks that I can see: > - we have to follow Whoosh syntax and not imagine ourselves, at least > in basics - may be it is not a drawback :) Given the qparser plugin system that you have already hinted at, it should not be so bad if we want to add syntax. > - Bloodhound Search plugin will depend on Whoosh even if other search > backend is used e.g. PyLucene > > If we can leave with this, I vote for starting prototype with Whoosh > syntax and parser since it will speedup features delivery. Anyway, we > can implement our own parser later. > > Regards, Andrej Yes, I entirely agree with that approach. I would be very happy to see some early search improvements! Cheers, Gary