From solr-user-return-140361-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Thu Apr 5 23:00:09 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 836C618063B for ; Thu, 5 Apr 2018 23:00:08 +0200 (CEST) Received: (qmail 98951 invoked by uid 500); 5 Apr 2018 21:00: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 98935 invoked by uid 99); 5 Apr 2018 21:00:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2018 21:00:00 +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 5CC77182564 for ; Thu, 5 Apr 2018 21:00:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.11 X-Spam-Level: X-Spam-Status: No, score=-0.11 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=openindex.io Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 2bqrdSVkUHXH for ; Thu, 5 Apr 2018 20:59:59 +0000 (UTC) Received: from mail1.ams.nl.openindex.io (mail1.ams.nl.openindex.io [141.105.125.41]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 20D485F5AF for ; Thu, 5 Apr 2018 20:59:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail1.ams.nl.openindex.io (Postfix) with ESMTP id 9E2C6380DEF; Thu, 5 Apr 2018 20:59:52 +0000 (UTC) Received: from mail1.ams.nl.openindex.io ([127.0.0.1]) by localhost (mail1.ams.nl.openindex.io [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XO5cSnfMnmUS; Thu, 5 Apr 2018 20:59:52 +0000 (UTC) Received: from mail1.ams.nl.openindex.io (localhost [127.0.0.1]) by mail1.ams.nl.openindex.io (Postfix) with ESMTP id 7984E380DD2; Thu, 5 Apr 2018 20:59:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=openindex.io; s=mail; t=1522961992; bh=6yYIKS9cEu6W/jFaBdPtJtsCKAT7FDlv5aLdlPMpJn8=; h=Subject:From:To:Cc:Date:From; b=WjA34BRFhFFoQSLslgTlJSh/Ic6c7pJ+/Usa4fBTZczmILjw94gAhRfBci7ONLMJ7 /zcpcyd0vCgOpo6MY4tR+3S4L9wUjpbNprhkJTTXVpoSz/jsUvyTxjFt7HwEJz9Pxc huBrMAZUw3Vhf/HAAfLvH/W7pzVJiJLgOzHpTX/+Cpx5WbG8yQNLP0kdM0OtZcyfqQ fwU8wqcJTQ6lLB6rqauiLXs0SMCspZIs2YQXLq2WlnVnCtB9iRfY7aycGLUo59VFkB vTBDWhTmNlJSJmVaJkHR32OTWynO0InsXL779eGvUNCAAKeU/oMr3BCXUK8GeLlAPe OBhRm7BLvmywg== Subject: RE: Storing Ranking Scores And Documents In Separate Indices From: =?utf-8?Q?Markus_Jelsma?= To: =?utf-8?Q?solr-user=40lucene=2Eapache=2Eorg?= Cc: =?utf-8?Q?Collazo=2C_Carlos?= , =?utf-8?Q?Ganesan=2C_VinothKumar?= Date: Thu, 5 Apr 2018 20:59:52 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-Mailer: Zarafa 7.2.1-51838 X-Original-To: Message-Id: Hello Quynh, Solr has support for external file fields [1]. They are a simple key=3Dfloat based text file where key is ID, and the float can be used for boosting/scoring documents. This is a much simpler approach than using a separate collection. These files can be reloaded every commit and are really easy to use. We use them for boosting documents by their popularity. Hope that helps, Markus [1] https://lucene.apache.org/solr/guide/6_6/working-with-external-files-and-processes.html =20 -----Original message----- > From:Huynh, Quynh > Sent: Thursday 5th April 2018 22:50 > To: solr-user@lucene.apache.org > Cc: Collazo, Carlos ; Ganesan, VinothKumar > Subject: Storing Ranking Scores And Documents In Separate Indices >=20 > Hey Solr Community, >=20 > We have a collection of product documents that we=E2=80=99d like to add fields to with ranking scores generated by our data scientists. >=20 > Two options we=E2=80=99re considering is to either: > - Have a separate index that contains all the documents from our product index, but with these additional ranking fields > - Have an index with just the score fields and a numerical key to represent the product that would require a separate lookup >=20 > We wanted to know if any Solr users with a similar problem has tried either of those options (and the performance implications you faced), or had a different approach to structuring documents in separate collections, where the only difference between the documents was the ranking fields. >=20 >=20 > Thanks! > Quynh >=20