Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 15CB1200CB4 for ; Tue, 27 Jun 2017 13:52:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1471E160BE9; Tue, 27 Jun 2017 11:52:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5ACDC160BDC for ; Tue, 27 Jun 2017 13:51:59 +0200 (CEST) Received: (qmail 48724 invoked by uid 500); 27 Jun 2017 11:51:57 -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 48713 invoked by uid 99); 27 Jun 2017 11:51:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2017 11:51:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 17C261A0469 for ; Tue, 27 Jun 2017 11:51:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.286 X-Spam-Level: ** X-Spam-Status: No, score=2.286 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id x-b--0gWSBwb for ; Tue, 27 Jun 2017 11:51:56 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D5F9C5FDA5 for ; Tue, 27 Jun 2017 11:51:55 +0000 (UTC) Received: from mben.nabble.com (unknown [162.253.133.72]) by mwork.nabble.com (Postfix) with ESMTP id 9F1C54DBF136C for ; Tue, 27 Jun 2017 04:51:54 -0700 (MST) Date: Tue, 27 Jun 2017 04:51:54 -0700 (MST) From: mganeshs To: solr-user@lucene.apache.org Message-ID: <1498564314656-4343005.post@n3.nabble.com> In-Reply-To: References: <1498230296315-4342563.post@n3.nabble.com> <1498456007593-4342778.post@n3.nabble.com> Subject: Re: Using of Streaming to join between shards MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 27 Jun 2017 11:52:00 -0000 Hi Susheel, Thanks for your reply and as you suggested we will start with innerJoin. But what I want know is that, Is Streaming can be used instead of normal default Join ? For ex. currently we fire request for every user clicks on menu in the page to show list of his documents with default JOIN and it works well without any issues with 100 concurrent users as well or even more than that concurrency. Can we do same for streaming join as well ? I just want to know whether concurrent streaming request will create heavy load to solr server or it's same as default join. What would be penalty of using streaming concurrently instead of default join ? Kindly throw some light on this topic. -- View this message in context: http://lucene.472066.n3.nabble.com/Using-of-Streaming-to-join-between-shards-tp4342563p4343005.html Sent from the Solr - User mailing list archive at Nabble.com.