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 F021D200CC2 for ; Wed, 5 Jul 2017 16:30:41 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EE6DF1636E8; Wed, 5 Jul 2017 14:30:41 +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 403691636E6 for ; Wed, 5 Jul 2017 16:30:41 +0200 (CEST) Received: (qmail 10527 invoked by uid 500); 5 Jul 2017 14:30:31 -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 10509 invoked by uid 99); 5 Jul 2017 14:30:29 -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; Wed, 05 Jul 2017 14:30:29 +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 624C218138F for ; Wed, 5 Jul 2017 14:30:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.102 X-Spam-Level: X-Spam-Status: No, score=-0.102 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=elyograg.org 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 oegNUhoNNvGe for ; Wed, 5 Jul 2017 14:30:25 +0000 (UTC) Received: from frodo.elyograg.org (frodo.elyograg.org [166.70.79.219]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 95A635FC93 for ; Wed, 5 Jul 2017 14:30:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by frodo.elyograg.org (Postfix) with ESMTP id AECBC1EE5 for ; Wed, 5 Jul 2017 08:30:15 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-language: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=1499265015; bh=1RnaECeflP2qb/EAGENoWOO+EXSA uaZrQkH2hrBinvg=; b=RMm4dzPHeCT32iLuLWU95tyhuj4ZECPaKkgMyAEHsBzw +BPDrkVKCNKLOM8D3yln1atGVFa6WEmHrQCsazvvwJxwhpIFMvLSA7LcAHkDDXKp gIMbXBEnBSzXq/GKxsklBr+BqAhHo7ljQH9yFaAcvB30iZ1+vEWNCDrHug5RHDI= 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 9whwrbsc3qSJ for ; Wed, 5 Jul 2017 08:30:15 -0600 (MDT) 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 CE34B1EBC for ; Wed, 5 Jul 2017 08:30:14 -0600 (MDT) Subject: Re: cursorMark / Deep Paging and SEO To: solr-user@lucene.apache.org References: From: Shawn Heisey Message-ID: <33b4ef92-7aec-9459-97e0-bb42b2f82637@elyograg.org> Date: Wed, 5 Jul 2017 08:30:00 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US archived-at: Wed, 05 Jul 2017 14:30:42 -0000 On 6/30/2017 1:30 AM, Jacques du Rand wrote: > I'm not quite sure I understand the deep paging / cursorMark internals > > We have implemented it on our search pages like so: > > http://mysite.com/search?foobar&page=1 > http://mysite.com/search?foobar&page=2&cmark=djkldskljsdsa > http://mysite.com/search?foobar&page=3&cmark=uoieuwqjdlsa > > So if we reindex the data the cursorMark for search "foobar" and page2 will > the cursorMark value change ??? > > But google might have already index our page as " > http://mysite.com/search?foobar&page=2&cmark=djkldskljsdsa" so that > cursorMark will keep changing ?? The cursorMark feature does not use page numbers, so your "page" parameter won't provide any useful information to Solr. Presumably you're using that for your own application. The string values used in cursorMark have a tendency to lose their usefulness the more you index after making the query, so they are not useful to have in Google's index. The cursorMark value points at a specific document ... if you index new documents or delete old documents, that specific document might end up on a completely different page number than where it was when you initially made the query. Thanks, Shawn