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 AFE531812A for ; Fri, 11 Dec 2015 18:53:55 +0000 (UTC) Received: (qmail 46602 invoked by uid 500); 11 Dec 2015 18:53:51 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 46545 invoked by uid 500); 11 Dec 2015 18:53:51 -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 46532 invoked by uid 99); 11 Dec 2015 18:53:50 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2015 18:53:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id ED394180A9A for ; Fri, 11 Dec 2015 18:53:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.901 X-Spam-Level: ** X-Spam-Status: No, score=2.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=griddynamics.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id f8eND3uf6aKe for ; Fri, 11 Dec 2015 18:53:38 +0000 (UTC) Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 00480429DD for ; Fri, 11 Dec 2015 18:53:37 +0000 (UTC) Received: by lfed137 with SMTP id d137so33944971lfe.3 for ; Fri, 11 Dec 2015 10:53:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=griddynamics.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=3XfR9LtfDoWvFCSspr6DH/Eow3QZ65CXDWTqJFGXw6o=; b=vSFxm97edJkv9vh5kfFk4bgmxSfYQdOSi6HcJpapiu8Q7lXuDPoKRzhlK1P/rvxwon ZHThDN/JRURUvil9Cl9Z9V5N2QlN8QLtH1GU/JcVKqFPwwcwPWGjs2aFDeu58sXgR+J0 CK33Orvml/+4NOMHQFvWUMwB6lqsqb1lElHpI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=3XfR9LtfDoWvFCSspr6DH/Eow3QZ65CXDWTqJFGXw6o=; b=MNiDna76TiScupptd5zG0Q2rRM+58CXpsLO7c82JJt8w5tmaBEwJoH8+wsR4hDMOFd mRkT/fyO/Pe8HY9VvLkWiZD1POCFLRyTjqncCIm2/MjuobKwPMk4ipm9SUTJyFZZ2jTQ 6PiI4+B/hCmjJOgeVK7ZmmZrUoz2Eg/JdivH/ZzRVKzD+WnioUzXo9aKxOWIyMJJlh7R QNJBdsf2ORRcpKf0DNDnroGONzblSLFhb65idbnIIAke2Vb0w7W5tUNUvnwVWOQgxWn+ B7vgQXljTke5WdLTHBopSVve3wY9jAL+wLk32LnAPyq5SdH1+cB2Zn1j7b1IpyPe7xYv GoVA== X-Gm-Message-State: ALoCoQkUwlEB6gWuhz2prP/McIMbuOR6CQy7jsYZGCA9CE6b5mNMGfp7JYN++1tsu1RSFzMdw9T7v1xw2FaD4DOrgQ3NmYDHuyYWl2dliCqHWve3KINPsGE= X-Received: by 10.25.138.68 with SMTP id m65mr8474901lfd.69.1449860010898; Fri, 11 Dec 2015 10:53:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.185.103 with HTTP; Fri, 11 Dec 2015 10:52:51 -0800 (PST) In-Reply-To: <566AEC63.4060303@temetra.com> References: <566AEC63.4060303@temetra.com> From: Mikhail Khludnev Date: Fri, 11 Dec 2015 21:52:51 +0300 Message-ID: Subject: Re: Block Join query To: solr-user Content-Type: multipart/alternative; boundary=001a113fb6aceca1d00526a3d63b --001a113fb6aceca1d00526a3d63b Content-Type: text/plain; charset=UTF-8 Novin, I regret so much. It's my pet peeve in Solr query parsing. Handling s space is dependent from the first symbol of query sting This will work (starts from '{!' ): q={!parent which="doctype:200"}flow:[624 TO 700] These won't due to " ", "+": q= {!parent which="doctype:200"}flow:[624 TO 700] q=+{!parent which="doctype:200"}flow:[624 TO 700] Subordinate clauses with spaces are better handled with "Nested Queries" or so, check the post On Fri, Dec 11, 2015 at 6:31 PM, Novin wrote: > Hi Guys, > > I'm trying block join query, so I have tried +{!parent > which="doctype:200"}flow:624 worked fine. But when i tried +{!parent > which="doctype:200"}flow:[624 TO 700] > > Got the below error > > org.apache.solr.search.SyntaxError: Cannot parse 'flow_l:[624': > Encountered \"\" at line 1, column 11.\nWas expecting one of:\n > \"TO\" ...\n ...\n ...\n > > Just wondering too, can we able to do range in block join query. > > Thanks, > Novin > > > > > -- Sincerely yours Mikhail Khludnev Principal Engineer, Grid Dynamics --001a113fb6aceca1d00526a3d63b--