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 B8886200CCE for ; Sun, 23 Jul 2017 17:01:28 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B6F931642A0; Sun, 23 Jul 2017 15:01:28 +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 052C616429E for ; Sun, 23 Jul 2017 17:01:27 +0200 (CEST) Received: (qmail 54531 invoked by uid 500); 23 Jul 2017 15:01:21 -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 53739 invoked by uid 99); 23 Jul 2017 15:01:20 -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; Sun, 23 Jul 2017 15:01:20 +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 8C4B3C0E0C for ; Sun, 23 Jul 2017 15:01:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.15 X-Spam-Level: ** X-Spam-Status: No, score=2.15 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 yAyOLcl0juaA for ; Sun, 23 Jul 2017 15:01:11 +0000 (UTC) Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 026A760D14 for ; Sun, 23 Jul 2017 15:01:06 +0000 (UTC) Received: by mail-wm0-f41.google.com with SMTP id c184so4726403wmd.0 for ; Sun, 23 Jul 2017 08:01:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=eDMZNGr5gj5kM1DqV9av+r5xKFH6Wl2rjvA0q74u5c8=; b=gojgg3v3TNKSPgOBgPEMOYCxDIlescswklPsVAALgYdO6h+DcF2i4ASxZIIxv06JdW QTX7K8a/JY8xPdXlfO1nOM9J0hn/04vJ1Gucv6regoRyXzjHJC2FwG6pRYnQ5iNIP925 QK8VDYZNgv+mSimzz+Pf9LtqwORV9l6HaQrdU3XTILl19DOrjWEb1FjZ2jbj2Vog33mK navf/5uJ1/FozydH3O7zCvh5ABnxjyED3YENyVv+IgbmhQKFAzLFBNi67xmODMuc7qd+ MZ8RTLJYT7HFGpLj4VtfRU27MbE3k8TIo7sZ7ad6grTJA58GNYtoFe03JhnWIm99bUCn P4YQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=eDMZNGr5gj5kM1DqV9av+r5xKFH6Wl2rjvA0q74u5c8=; b=hq7O6cidoUoxQnvuOHCCuv8tETuyfEn/CA/3K/xCh5A6ahxPutBTE6c7NfoauwL8Xd Qx/rUEMuqbQ0aDMOeMoeuUCYHONVV322lx5Ogqof3HZVrCpQXNLf/2nc9xZuhRR3q+Yl qauUuKCCpMbd3MxJ51FtWbOeT2NEky441nrYMaDXznRQ7ZarhveZTLLxIFKJXqoEWomE aspSTXYKazxk9zF4JT9znJU/70mjrjcCh8bhSPR3M8vjv/JH70FMFcfyaU8pGl38gbtc F9j7o4GoI4KHz3UsLBDVJDsElQhIrdZP38Xr3MopCbD/c8hVjwZngTNJ/aHCtEn+vNY8 K2WQ== X-Gm-Message-State: AIVw112dwIHaBJjF2reEunQhNzsstfkcgasH0SscNtI8UVknYru4Q11a ue3nlJTLHD6ZILF9v9Si06+e+WBKOQYZ X-Received: by 10.80.215.68 with SMTP id i4mr11188618edj.258.1500822065506; Sun, 23 Jul 2017 08:01:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.177.162 with HTTP; Sun, 23 Jul 2017 08:01:05 -0700 (PDT) In-Reply-To: <28c36880-7955-32b0-51c1-feea5a151ca3@elyograg.org> References: <1899970789.1274135.1500537091057@mail.yahoo.com> <375645941.1568006.1500563376393@mail.yahoo.com> <4B14EAD9-9277-4C81-8275-F0007268A9DD@wunderwood.org> <1500721376250-4347250.post@n3.nabble.com> <28c36880-7955-32b0-51c1-feea5a151ca3@elyograg.org> From: Susheel Kumar Date: Sun, 23 Jul 2017 11:01:05 -0400 Message-ID: Subject: Re: Need guidance solrcloud shardings with date interval To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary="f403045dc8c815eef80554fd5ece" archived-at: Sun, 23 Jul 2017 15:01:28 -0000 --f403045dc8c815eef80554fd5ece Content-Type: text/plain; charset="UTF-8" If you decide to go with multiple collection and aliasing, this would be useful https://blog.cloudera.com/blog/2013/10/collection-aliasing-near-real-time-search-for-really-big-data/ On Sat, Jul 22, 2017 at 10:37 AM, Shawn Heisey wrote: > On 7/22/2017 5:02 AM, m rehman kahloon wrote: > > but my R&D is to find a way, not to use shard name using loading > > time,solrcloud automatically load data into predefined shard/date > specific > > shard. > > The implicit router is the only one you can use when you're doing time > interval sharding, because it's the only one that allows the addition of > new shards after collection creation. > > There is a reason that we are considering renaming the "implicit" router > to "manual" instead. > > https://issues.apache.org/jira/browse/SOLR-6630 > > When you use the implicit router, you're completely in charge of > sharding. There is no automation. You must name the shards, create > them, delete them, and inform Solr during indexing about which shard > will get new documents. If you want to only query a subset of the > shards in a collection, you are responsible for telling Solr that with > the shards parameter on the query. > > If you want to come up with a way to patch the Solr source code to add a > new router that does automated time interval sharding, that will be > welcome. > > Thanks, > Shawn > > --f403045dc8c815eef80554fd5ece--