From solr-user-return-144514-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Mon Oct 22 20:20:08 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 39C3918064A for ; Mon, 22 Oct 2018 20:20:08 +0200 (CEST) Received: (qmail 4272 invoked by uid 500); 22 Oct 2018 18:20:06 -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 3674 invoked by uid 99); 22 Oct 2018 18:20:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2018 18:20:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C8F1FC298F for ; Mon, 22 Oct 2018 18:20:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.898 X-Spam-Level: * X-Spam-Status: No, score=1.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=iq.media Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id bpODU42I3eqQ for ; Mon, 22 Oct 2018 18:20:03 +0000 (UTC) Received: from mail-wm1-f50.google.com (mail-wm1-f50.google.com [209.85.128.50]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id A59F45F117 for ; Mon, 22 Oct 2018 18:20:03 +0000 (UTC) Received: by mail-wm1-f50.google.com with SMTP id 189-v6so11313513wmw.2 for ; Mon, 22 Oct 2018 11:20:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iq.media; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=LnYE6d1UgVWDJyPAnlV/qYVGoomLUSDTLBGz5GJtoDg=; b=Y+Wb35FMnlCjQiaQYiH+s+TVh3qPW6cAv6Ij3IBuMUAaPg4Sjl5nMlC2syF8ezUF7p 6myL0D25jjq92GmxhQ2jjaVcPuwZBiPxE6COlBNaByct72bzwWSv+bKmM2qzm2qaafCX WBsagSQze3OXOdvPo6jEWK6YhRcJdf/MGYAgE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=LnYE6d1UgVWDJyPAnlV/qYVGoomLUSDTLBGz5GJtoDg=; b=XNrWt1EO+TR6PT2U30GQSSK5wZy8K81Z7j7HPQv3X0Wtmcm3ySG6tmtfEZ0M4Z7awM WgKqvKmue/NWxUBvCILeuv4KzwpUJ8jgxUkxcC5pkRoBpPwNoBnoAnAVCk7/7Tz/L8Fa R0A6s2KdO3gRLuM78jTNqCIZVxSuqi6mb7MEL2QIJhnPUgN0rcdRJ6AIfMPu5UqRtVzJ UVfzyQBS27M9UREEPoL3F2xYdqcmD97Gu1BzywMU11u+/roWCauOhJwJLxF/SRqrm7WX eWWzch8hpe3kL2DGk6MLGyHpRyxuFm/zNKMLc5En8P4jfflfRTAK/80saqeFJwQ/0d5m crvA== X-Gm-Message-State: ABuFfohF/ZVx6uI6HknFApOpOpz7LeYm7bRdklY1ltU5Dkh8cSdhd1az shmSZCXEv85J+z1FYmVrY6J8dKngXjqccLzou6yfmn/Z X-Google-Smtp-Source: ACcGV619G8LETCxIUIl6JvCpUHIZoZyrHUZrd57oqF5ZRtWqEo/IQTFfh2LvqKwXO5+0rTYxKqWuLeIl0XmIeFHvcqk= X-Received: by 2002:a1c:2ecc:: with SMTP id u195-v6mr17661771wmu.137.1540232402505; Mon, 22 Oct 2018 11:20:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Chris Ulicny Date: Mon, 22 Oct 2018 14:19:49 -0400 Message-ID: Subject: Re: Query to multiple collections To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary="0000000000003926af0578d54dbd" --0000000000003926af0578d54dbd Content-Type: text/plain; charset="UTF-8" Rohan, I do not remember where I came across it or what restrictions exist on it, but it works for our use case of querying multiple archived collections with identical schemas in the same SolrCloud cluster. The queries have the following form: http::/solr/current/select?collection=current,archive2,archive4&q=... It seems like it might work for your use case, but you might need to tread carefully depending on your requirements for the returned results. Sorting and duplicate unique keys come to mind. Best, Chris On Mon, Oct 22, 2018 at 1:49 PM Rohan Kasat wrote: > Hi All , > > I have a SolrCloud setup with multiple collections. > I have created say - two collections here as the data source for the both > collections are different and hence wanted to store them differently. > There is a use case , where i need to query both the collections and show > unified search results. > The fields in the schema are same. ( say - title , description , date ) > Is there any specific way i can do this directly with the collections API > or something like that? > Or i need to write a federator and combine results from search to the > respective collections and then unify them? > > -- > > *Regards,Rohan* > --0000000000003926af0578d54dbd--