Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A72D0700F for ; Thu, 17 Nov 2011 20:53:50 +0000 (UTC) Received: (qmail 45783 invoked by uid 500); 17 Nov 2011 20:53:49 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 45713 invoked by uid 500); 17 Nov 2011 20:53:49 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 45676 invoked by uid 99); 17 Nov 2011 20:53:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2011 20:53:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bw0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2011 20:53:43 +0000 Received: by bkbc12 with SMTP id c12so3690606bkb.35 for ; Thu, 17 Nov 2011 12:53:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=03HTVDSWJlC6IgCKwRmzNdgf3tAJwI50NyUuWYD4ADY=; b=CudhpUlGLyC0n8ppoPTx0cdEiJZo4+SE5teC/xZLcMi+7Moslj30SryqNMIcau+AZm TgdmLsgmVBZT0xn60GdXsPMXQ/7b1berYoYlRMyyY+iIVRQM57ZqCih5u2aWHNvA+sQD vIuj1Jg6Nxg9hPjL/0qVyT1WTsLQJPBw93lGU= MIME-Version: 1.0 Received: by 10.205.126.15 with SMTP id gu15mr169505bkc.108.1321563201769; Thu, 17 Nov 2011 12:53:21 -0800 (PST) Reply-To: yonik@lucidimagination.com Sender: yseeley@gmail.com Received: by 10.223.145.150 with HTTP; Thu, 17 Nov 2011 12:53:21 -0800 (PST) In-Reply-To: <81A74735-7CA5-4538-96E3-2603C378078D@yahoo.co.uk> References: <78D33D3D-47FF-42AA-B7D9-9AEFA51991F8@robustlinks.com> <4EC3CE86.9010907@fissore.org> <4EC402AF.5000404@yahoo.de> <4EC41E9F.1020002@yahoo.de> <4EC4D30F.4000905@yahoo.de> <005901cca566$017c91d0$0475b570$@thetaphi.de> <81A74735-7CA5-4538-96E3-2603C378078D@yahoo.co.uk> Date: Thu, 17 Nov 2011 15:53:21 -0500 X-Google-Sender-Auth: psaRWabYdUI3l_OEzztcPHOW_Ys Message-ID: Subject: Re: ElasticSearch From: Yonik Seeley To: java-user@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Thu, Nov 17, 2011 at 3:40 PM, Mark Harwood wrote: > JSON or XML can reflect more closely the hierarchy in the underlying Lucene query objects. We normally use the Lucene QueryParser syntax itself for that (not HTTP parameters). Other parameters such as filters, faceting, highlighting, sorting, etc, don't normally have any hierarchy. I don't think JSON is always nicer either. How would you write this sort in JSON for example? sort=price desc, score desc A big plus to Solr's APIs is that it's relatively easy to type them in to a browser to try them out. As far as alternate query syntaxes (as opposed to alternate request syntaxes), Solr has good support for that and it would be simple to add in support for a JSON query syntax if someone wrote one. AFAIK, there's an issue open for adding the XML query syntax, but I'm not sure if it's ever had much traction. -Yonik http://www.lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org