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 B03C4FDD4 for ; Wed, 21 Aug 2013 19:09:05 +0000 (UTC) Received: (qmail 50430 invoked by uid 500); 21 Aug 2013 19:09:01 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 50380 invoked by uid 500); 21 Aug 2013 19:09:01 -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 50372 invoked by uid 99); 21 Aug 2013 19:09:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 19:09:01 +0000 X-ASF-Spam-Status: No, hits=2.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,TRACKER_ID X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rafael.calsaverini@gmail.com designates 209.85.217.171 as permitted sender) Received: from [209.85.217.171] (HELO mail-lb0-f171.google.com) (209.85.217.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 19:08:55 +0000 Received: by mail-lb0-f171.google.com with SMTP id t13so945890lbd.30 for ; Wed, 21 Aug 2013 12:08:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=q18Fw61I5SVI7zh1APh/LuGCsA5Nhvke4VOssCc6Mn4=; b=l1P7F/nTohtpyOCgFcFy4tCkXTw5HlHnoZiO8XaEXu6T72Ur/fltTmJFtz/ds48y9b NxIyj5eBMncI9tbAr34EQeK7cvxmsOF4DGsdLBeRjaDtdlKnozXmuRGSwgSZT4x7UUPA czvpw91jnP0WODdJfKhb6T6PPrbGdhcTmqeGkLy61NJBDtaUexyCnXzeDwQNW9nIjliq nwRqZSp/FsflcrXSNvK8Xxk0F0tJ8GAM3+a4DKQGj1nZKKQPUA3kFxQo4A+t5lP5aBRA 81ModJg7L1Hj97rF1klsrEckGO2UyiCtyZuJUbJmAJZp4qt559aFov4kR/FvXLnbTLP7 rOJA== X-Received: by 10.152.2.201 with SMTP id 9mr7172420law.20.1377112115330; Wed, 21 Aug 2013 12:08:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.199.16 with HTTP; Wed, 21 Aug 2013 12:08:15 -0700 (PDT) In-Reply-To: References: From: Rafael Calsaverini Date: Wed, 21 Aug 2013 16:08:15 -0300 Message-ID: Subject: Re: edismax type query in different sets of fields? To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=089e013c676073438604e479e6fc X-Virus-Checked: Checked by ClamAV on apache.org --089e013c676073438604e479e6fc Content-Type: text/plain; charset=ISO-8859-1 Hum! It seems to be exactly what I need. Thanks! I'll look for it in the docs. Rafael Calsaverini Data Scientist @ Catho cell: +55 11 7525.6222 * * *8d21881718d00d997686177be1c27360493b23ea0258f5e6534437e6* On Wed, Aug 21, 2013 at 12:08 PM, Erick Erickson wrote: > Have you tried "nested queries"? I think you can specify the full edismax > syntax on the URL in a nested query for your second search field... > > Best, > Erick > > > On Tue, Aug 20, 2013 at 5:17 PM, Rafael Calsaverini < > rafael.calsaverini@gmail.com> wrote: > > > Hi there, > > > > > > suppose I have documents with fields that can be loosely grouped by what > > kind of information they contain. As an example, imagine the documents > > representing people and some fields are related to how they're called > > (name, surname, nickname, etc...) and some fields are related to where > they > > live (street, city, state, ...). > > > > Imagine I have an application that provide two search fields to look for > > people: who do you want to find, and where does he live. So I just get > two > > strings, and each of them might contain information related to multiple > > fields. > > > > Is there a way to do something like edismax for each group of field? > > Something like: > > > > (name^2 surname^2 nickname):(rafael calsaverini) AND (street city > > state):(rua dos bobos sao paulo SP) > > > > or whatever is the adequate syntax. > > > > The alternative would be to build a parser for one of the fields, but if > I > > want to allow for a completely free field for the "where" part, it might > > not be easy to predict what the user would put there. Is there anybody > else > > with a similar problem? > > > > Thanks. > > > > > > > > Rafael Calsaverini > > Data Scientist @ Catho > > cell: +55 11 7525.6222 > > > > * > > * > > *8d21881718d00d997686177be1c27360493b23ea0258f5e6534437e6* > > > --089e013c676073438604e479e6fc--