Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAEZ-ge7a2W8dyj0T5Oph2zeQDPGHqyyZ_vNwYM_exmQ9in+i6w@mail.gmail.com>
References: <20121128151735.03AEB803AF@bloodhound-vm>
	<CAGMZAuOaD5P4ZF3EEcQfwkS0+ARwhQ7pZcsLDT0ri6+fabPX1g@mail.gmail.com>
	<50BE0908.7090900@wandisco.com>
	<CAHM0gnhRD2=zxsY77xd0APw7gmnkn2GYYS8wH9KSDdS55CT2rQ@mail.gmail.com>
	<CAEZ-ge7a2W8dyj0T5Oph2zeQDPGHqyyZ_vNwYM_exmQ9in+i6w@mail.gmail.com>
Date: Wed, 5 Dec 2012 14:43:51 +0100
Message-ID: 
 <CAHM0gnjRX9ch4PQmnyopfT=xDJGOCGjr95pkRx+SZzZoSgzoFg@mail.gmail.com>
Subject: Re: [Apache Bloodhound] Proposals/BEP-0004/ResourceQuery added
From: Andrej Golcov <andrej@digiverse.si>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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 :)
 - 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