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 490D6109DB for ; Thu, 10 Oct 2013 08:28:30 +0000 (UTC) Received: (qmail 43039 invoked by uid 500); 10 Oct 2013 08:28:17 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 42970 invoked by uid 500); 10 Oct 2013 08:28:14 -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 42944 invoked by uid 99); 10 Oct 2013 08:28:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Oct 2013 08:28:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pvkdevi@gmail.com designates 209.85.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vb0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Oct 2013 08:28:07 +0000 Received: by mail-vb0-f47.google.com with SMTP id h10so1340384vbh.20 for ; Thu, 10 Oct 2013 01:27:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=e9IuZ+bBwzOc/ob9B2IAZbcoHTRh9LS5A+LfPq05Uac=; b=lc8Ox7vACr+s2V0RA+QkXZNwStpKyvt3PY6b7L+NdBiiVvlz8HI9H0UYINyl1oxtyz cHB9eZKAjbD8IhByq4InkCfsQY6L85VZkcLkja77GQpeasDIhWhPIIrIZOZw4GWML4El FOrjcIKW03aXfgk7+Rj0B5ZvFIyk3SeKHw6pGRjM1klhX7NCq1HQsFp2pW/G3TTH8Jft nxb9P371qjvzn7HVw+L6QT7ogpd6/RgH9r7vW4wjS2lKb6TwSM38CDwLn0hAuY4e/mmd fihFeMxHRao6xZPQNqZDigXeZVj1l8cGuP0za5RF25DaBbFS72aWGVqTdcpMe6l4vFC9 E5Rg== MIME-Version: 1.0 X-Received: by 10.220.43.140 with SMTP id w12mr4608294vce.87.1381393666691; Thu, 10 Oct 2013 01:27:46 -0700 (PDT) Received: by 10.221.10.207 with HTTP; Thu, 10 Oct 2013 01:27:46 -0700 (PDT) Date: Thu, 10 Oct 2013 13:57:46 +0530 Message-ID: Subject: queries with "&&" doesn't work but "AND" does From: Devi pulaparti To: java-user@lucene.apache.org Content-Type: multipart/alternative; boundary=047d7b3a8748cc57ce04e85ec6bb X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3a8748cc57ce04e85ec6bb Content-Type: text/plain; charset=ISO-8859-1 In our search application, queries like test && usage do not return correct results but test AND usage works fine. So queries with "&&" doesn't work but "AND" does. We are using default queryparser with standard analyzer. Could some one please help me resolving this. please let me know if you need more details of implementation. --047d7b3a8748cc57ce04e85ec6bb--