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 C105E1857B for ; Fri, 26 Feb 2016 23:06:28 +0000 (UTC) Received: (qmail 13575 invoked by uid 500); 26 Feb 2016 23:06:24 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 13507 invoked by uid 500); 26 Feb 2016 23:06:24 -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 13489 invoked by uid 99); 26 Feb 2016 23:06:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Feb 2016 23:06:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1E53EC093B for ; Fri, 26 Feb 2016 23:06:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.078 X-Spam-Level: ** X-Spam-Status: No, score=2.078 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L3=2.499, RP_MATCHES_RCVD=-0.329, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=elyograg.org Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 5NCkewTCFQi0 for ; Fri, 26 Feb 2016 23:06:20 +0000 (UTC) Received: from frodo.elyograg.org (frodo.elyograg.org [166.70.79.219]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 4EECB5FAE4 for ; Fri, 26 Feb 2016 23:06:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by frodo.elyograg.org (Postfix) with ESMTP id 3F69418F for ; Fri, 26 Feb 2016 16:06:15 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject:received:received; s=mail; t= 1456527975; bh=jdHCavU1dJvPGkp7hpr+j1McULb4u6BmSkKD4neSf6Y=; b=g jiE9ZMYrPie7prdArKuZ/okjdyoE4ptbs2gF+SoJgUZFFCJlM9OMgHYJZV41fN0f dWtGW6dSN4qojPnLS+QPz0HGn/rSZ5vuQUSKnXaWx9MDIqAb8bRvlTe9CCs1zmlM pJ6nNArxVy5w8otzHbHvgNcypjPxa+UcB1FgP5OT9Q= X-Virus-Scanned: Debian amavisd-new at frodo.elyograg.org Received: from frodo.elyograg.org ([127.0.0.1]) by localhost (frodo.elyograg.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id awQC5l39oQeR for ; Fri, 26 Feb 2016 16:06:15 -0700 (MST) Received: from [10.2.0.108] (client175.mainstreamdata.com [209.63.42.175]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: elyograg@elyograg.org) by frodo.elyograg.org (Postfix) with ESMTPSA id BD48CF4 for ; Fri, 26 Feb 2016 16:06:14 -0700 (MST) Subject: Re: Newest docs added To: solr-user@lucene.apache.org References: <1456527181285.70761@statsbiblioteket.dk> From: Shawn Heisey Message-ID: <56D0DA64.7020501@elyograg.org> Date: Fri, 26 Feb 2016 16:06:12 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <1456527181285.70761@statsbiblioteket.dk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 2/26/2016 3:53 PM, Toke Eskildsen wrote: > MarkG wrote: >> Is there a way anyone can recommend to identify newly added docs to a Solr >> index. Ie: I have some new docs. I update the index with the new doc and >> this happens on a regular basis, say every 4 weeks. I want to be able to >> distinguish the docs that are new given in a certain number of days, say 10 >> days from the time the index had the new doc added. > https://lucene.apache.org/solr/4_7_0/solr-core/org/apache/solr/update/processor/TimestampUpdateProcessorFactory.html > and a 'timestamp:[NOW/DAY-10DAYS TO *]' query? I didn't know about the timestamp update processor. That's pretty cool, and now that I really think about it, would be required for SolrCloud to operate sanely. If you're not running SolrCloud, then it can be handled with a config that's even easier. You can add a field like the following to your schema, and make sure that your indexing never includes this field: That's copied straight out of one of the schemas I'm using. Thanks, Shawn