Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of rcmuir@gmail.com designates
 74.125.82.176 as permitted sender)
Received-SPF: pass (google.com: domain of rcmuir@gmail.com designates
 10.180.77.228 as permitted sender) client-ip=10.180.77.228;
MIME-Version: 1.0
In-Reply-To: 
 <CAF=Pa59KT3quiAxBCO-HwWiW_01VvjZST7Nr4tr5Hhdu38J=2Q@mail.gmail.com>
References: 
 <CAF=Pa59KT3quiAxBCO-HwWiW_01VvjZST7Nr4tr5Hhdu38J=2Q@mail.gmail.com>
From: Robert Muir <rcmuir@gmail.com>
Date: Thu, 23 Feb 2012 13:41:19 -0500
Message-ID: 
 <CAOdYfZWe-axDR_8WnqOxVwTgHDw_PUw9XpEfFBfj3AKabtNi1g@mail.gmail.com>
Subject: Re: FieldCache future?
To: dev@lucene.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 23, 2012 at 1:32 PM, Ryan McKinley <ryantxu@gmail.com> wrote:
> In LUCENE-3360, there is discussion that DocValues could be used to
> replace the existing FieldCache. =C2=A0This seems like is a great
> direction, but I am not sure how people see this getting implemented.
>
> Is the suggestion to add something like:
> =C2=A0DocValues fieldCache(String field);
> to AtomicReader?

No, my suggestion is not to add anything to indexreader at all.
IndexReader is decoupled from FieldCache, I think we should keep it
that way.

You can already sort, group, etc on docvalues fields... so I'm arguing
that users should say up front which fields they are going to
sort/group on
so we can actually be an index and compute this stuff at indexing
time, rather than uninverting at search time (and do this stuff more
effectively with ideas like LUCENE-3729).

Thus this "compute/uninvert on the fly" fieldcache could be moved
somewhere else.

Grouping etc could work solely on a docvalues api and maybe they have
a special ctor to take a SortedBytes impl (and fieldcache implements
the docvalues api or some other backwards mechanism).
This would remove the redundant implementations (both fieldcache and
DV implementations) in stuff like grouping, join, sort, etc

Sure its a change, but so is making IndexReader read-only and other
things we have done.

--=20
lucidimagination.com

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