Aaron, We are trying to externalize RowId to Shard mapping, instead of current hashing algo.
We thought of storing this in a META shard, where lucene's in-memory postings format can be used. Also BlurClient can cache these mappings so there are progressively fewer trips to the meta-shard. -- Ravi On Fri, Jun 27, 2014 at 6:35 PM, Aaron McCurry <[email protected]> wrote: > When you get a change let us know what the use case is that you are solving > and perhaps we can add a feature to handle it. > > Aaron > > > On Fri, Jun 27, 2014 at 7:57 AM, Ravikumar Govindarajan < > [email protected]> wrote: > > > Thanks Tim, > > > > Shall surely do that. That should suffice > > > > -- > > Ravi > > > > > > On Fri, Jun 27, 2014 at 3:21 PM, Tim Williams <[email protected]> > > wrote: > > > > > On Friday, June 27, 2014, Ravikumar Govindarajan < > > > [email protected]> wrote: > > > > > > > We have a use-case whereby there is a need for a META shard. We don't > > > store > > > > row-documents here as other normal shards, but some arbitrary > > searchable > > > > meta-data > > > > > > > > Is it possible in Blur to do this? > > > > > > > > > > Hi Ravi, > > > Why not just create a "meta" table and put it in there with a 1-1 > > > row-record relationship? > > > > > > Thanks, > > > --tim > > > > > >
