Return-Path: 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 378CF10E12 for ; Thu, 6 Mar 2014 02:41:18 +0000 (UTC) Received: (qmail 66648 invoked by uid 500); 6 Mar 2014 02:41:16 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 66035 invoked by uid 500); 6 Mar 2014 02:41:15 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 66028 invoked by uid 99); 6 Mar 2014 02:41:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 02:41:14 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of erickerickson@gmail.com designates 209.85.128.170 as permitted sender) Received: from [209.85.128.170] (HELO mail-ve0-f170.google.com) (209.85.128.170) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 02:41:07 +0000 Received: by mail-ve0-f170.google.com with SMTP id pa12so2039916veb.1 for ; Wed, 05 Mar 2014 18:40:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=2aBO7lFbg5gCO0gZMx4W9/yotuj4KUrR/k082kxqiok=; b=clYA6uZ5cugXZcBbyLLGbGJKq5YEZXmcVDQ5BHzgKLq9Yo0B++8PB0TTXu1NXms+xv EnjY3AUB9O2oFkdqkt4AfhvR2eWsQBfOVCuir9DpWBEo9cZnq9ZmfQugeYEhlzAoSY/z CB8h2K4sB4WyGQXZ9uVMh0cKDChIhEx2TgBsbrKej2YhNJGgEHkDZ69kbE5s0uv7L+zJ RWywAlBA7mG1Ts8uoe0FArpkky8u4vCHVUdUWEm7CZqNhVIP+6jABRjP3HZEjKXUdxS0 byP5ZpbMOhiU+lkx54V3/ctwogeGgBwFoFOUb5DnRC1NKcEL3Zgt6Q3jAUvXZ0KKMAf9 K/Bw== MIME-Version: 1.0 X-Received: by 10.52.30.230 with SMTP id v6mr6143151vdh.6.1394073646752; Wed, 05 Mar 2014 18:40:46 -0800 (PST) Received: by 10.52.94.65 with HTTP; Wed, 5 Mar 2014 18:40:46 -0800 (PST) Date: Wed, 5 Mar 2014 21:40:46 -0500 Message-ID: Subject: abusing Doc values and updating fields.... From: Erick Erickson To: dev@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I had an odd thought and wondered if there's any possibility of abusing DocValues to make it work. And remember I have very little real clue about DocValues implementations.... We've seen requests to add a field to the Solr schema or change a field value, something akin to "update table set col1=foo where col2=bar" or "add a new field to Solr documents and populate it". It seems possible to write something that uses DocValues to actually do something like this. I'm completely fuzzy on what that would look like, whether one could do this on fields that weren't already DocValues="true" fields, etc. But it would be nifty if we could. And what a GSoC project if it makes any kind of sense! Erick@TiredEnoughThatAnySuggestionSeemsPossible --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org