Return-Path: 
 <dev-return-107584-apmail-lucene-dev-archive=lucene.apache.org@lucene.apache.org>
X-Original-To: apmail-lucene-dev-archive@www.apache.org
Delivered-To: apmail-lucene-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 99BD6DD55
	for <apmail-lucene-dev-archive@www.apache.org>;
 Sat,  1 Sep 2012 00:38:59 +0000 (UTC)
Received: (qmail 99423 invoked by uid 500); 1 Sep 2012 00:38:58 -0000
Delivered-To: apmail-lucene-dev-archive@lucene.apache.org
Received: (qmail 99374 invoked by uid 500); 1 Sep 2012 00:38:58 -0000
Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:dev@lucene.apache.org>
List-Id: <dev.lucene.apache.org>
Reply-To: dev@lucene.apache.org
Delivered-To: mailing list dev@lucene.apache.org
Received: (qmail 99367 invoked by uid 99); 1 Sep 2012 00:38:58 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Sep 2012 00:38:58 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [209.85.160.48] (HELO mail-pb0-f48.google.com) (209.85.160.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Sep 2012 00:38:50 +0000
Received: by pbbrq13 with SMTP id rq13so6714897pbb.35
        for <dev@lucene.apache.org>; Fri, 31 Aug 2012 17:38:29 -0700 (PDT)
Received: by 10.68.229.228 with SMTP id st4mr20415133pbc.106.1346459909867;
        Fri, 31 Aug 2012 17:38:29 -0700 (PDT)
Received: from frisbee.local (250.185-62-69.ftth.swbr.surewest.net.
 [69.62.185.250])
        by mx.google.com with ESMTPS id kt8sm4478461pbc.1.2012.08.31.17.38.28
        (version=SSLv3 cipher=OTHER);
        Fri, 31 Aug 2012 17:38:29 -0700 (PDT)
Date: Fri, 31 Aug 2012 17:38:27 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: dev@lucene.apache.org
Subject: Re: UUIDField uniqueKey with default="NEW"
In-Reply-To: <1346459582.5623.YahooMailClassic@web121703.mail.ne1.yahoo.com>
Message-ID: <alpine.DEB.2.02.1208311735040.13721@frisbee>
References: <1346459582.5623.YahooMailClassic@web121703.mail.ne1.yahoo.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Checked: Checked by ClamAV on apache.org


: I tested this approach (At revision 1379678) and it seems working. I can 
: see generated values. e.g. <str 
: name="uniqueKey">a259aa91-353f-4824-9f68-01837b721cf7</str>

Hmmm... on a single node instance it might work -- but i'm pretty sure 
it's just "tricking" the processing chain into thinking the uniqueKey for 
the document is "NEW" (literally the string "NEW") and then later in the 
processing the logic in UUIDField is replacing it with a new value.

If you tried to do that in SolrCloud, every document in your index would 
be routed to a single shard (based on the hash value of the string "NEW") 
and most of your documents would be un-deletable by id -- because your 
request to delete "a259aa91-353f-4824-9f68-01837b721cf7" would be routed 
to a diff shared then the one where the document wound up when Solr 
thought it's id was "NEW"



-Hoss

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org