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 BFD3317882 for ; Fri, 10 Oct 2014 10:18:52 +0000 (UTC) Received: (qmail 45829 invoked by uid 500); 10 Oct 2014 10:18:50 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 45762 invoked by uid 500); 10 Oct 2014 10:18:50 -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 45751 invoked by uid 99); 10 Oct 2014 10:18:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 10:18:49 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.217.182] (HELO mail-lb0-f182.google.com) (209.85.217.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 10:18:24 +0000 Received: by mail-lb0-f182.google.com with SMTP id z11so2703336lbi.41 for ; Fri, 10 Oct 2014 03:18:23 -0700 (PDT) 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:content-transfer-encoding; bh=4gQv2ycEOJK75Ilon1Nap7xGBtniEoKitMy7kxR1W88=; b=TUgrM3SUktXW+52CQsBQWIc7fNchEIxSCPODc0MEnA1FjqOg3h+mll7mUi/Ox2FxvX FsY4iIKLQA6vn4oo+nqbADs+ynrhJMHAyLs471DrCdPfRDrZdbLEGNrUZ08APi99Y5ps 3PyYIuixp1OtzY2vIA2z5v7DygHcVrYd55MrgIPfbjDSAZGlBbdqfVkxKhnEK8qTFkWj iaACWWcd1mVa6wgkTiXFgv0Rr2016hhCOoSYZj7a4lpZbpP3i01Oi/UiDgdammJSFcvR JrLfyPH3D4GwFoheiLAQsQTUMS8UiQOaDgqLhvVqsFE1QGBO4mwffIsJDXP/fCJAqNHi zlVQ== X-Gm-Message-State: ALoCoQmFrHVzC+aMqDRLLEumxD3JkKa3FIfa9ga3jbnivAYKHaRmkR8OPBCs2PGhITbg9uEBkvLW X-Received: by 10.112.17.2 with SMTP id k2mr3657237lbd.28.1412936303633; Fri, 10 Oct 2014 03:18:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.22.166 with HTTP; Fri, 10 Oct 2014 03:18:03 -0700 (PDT) In-Reply-To: <28a2971e14526f40f7e30d3559836c57@francelabs.com> References: <28a2971e14526f40f7e30d3559836c57@francelabs.com> From: Michael McCandless Date: Fri, 10 Oct 2014 06:18:03 -0400 Message-ID: Subject: Re: Search with term intersection To: Lucene Users Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org By intersection, do you mean a MUST clause on a BooleanQuery? Lucene uses "doc at a time" scoring, so for BooleanQuery, all MUST'd clauses are visiting the same doc (if they match) at a time, so we do the intersection for that document all at once, within each segment, across the N clauses. Mike McCandless http://blog.mikemccandless.com On Fri, Oct 10, 2014 at 5:02 AM, wrote: > Hi, > > I know that Lucene uses a skip-list algorithm to search very fast even if > the query needs to calculate intersection between terms within a segment. > But what happened if it needs to calculate an intersection between more t= han > one segment? I suppose that skip-list cannot be used anymore. Which data > structure is used? Bitset? > > Thank you for your answer. > > Aur=C3=A9lien > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org