I don't understand why you're having trouble with this.
You have a simple geo location search based on zip and then a product and 
inventory count.
I mean its not really geo-spatial because you're searching based on zip code.  
So you don't need to worry about any sort of geospatial or geodetic components.

Note: This really isn't a problem that is solved by HBase but better solved by 
a relational model (RDBMs)

This sounds more like a homework problem than a real problem....

But here's a free clue.
You don't index on inventory count. 
You filter the vendors on the client side or just add a filter to your query.

Sorry but as you describe it, its really a trivial problem.
(Which is why I think its a homework assignment.)

-Mike


> Date: Tue, 30 Aug 2011 00:57:37 -0600
> Subject: Re: Real time dynamic data and hbase
> From: [email protected]
> To: [email protected]
> 
> Thanks for the response Sonal.  Here is an example.
> 
> The client (backend) is online grocers.  The front end client is shoppers /
> consumers.
> 
> The grocers have an interface that they can log into and enter their
> inventory.  Example:  Apple = 9
> 
> The front end is simple; two values the users enter:
> 
> Product:  Apples
> Delivers to zip code:  90210
> 
> Once the query is submitted, the search results will display all the grocers
> that deliver apples to the users area code.
> 
> Whenever a grocer's supply (for any product) decreases to zero, they need to
> be dropped our of the results.  We do not want grocers showing quantity
> zero.  We only want grocers with a supply on hand.
> 
> Now...  Should the grocer that was dropped out because of a 0 value get a
> shipment and now have product on hand, once they enter the amount of their
> product, the non zero value should trigger the Db / search to include the
> grocer in the search again.
> 
> How would I go about doing this without have multiple tables for the same
> grocer or constantly re-indexing?
> 
> Am I going at this the wrong way completely?
> 
> Thanks again for the response and for and suggestions.
> 
> H-p
> 
> 
> 
> As orders come through for apples and the number decreases, one it hits 0,
> the clients
> 
> 
> 
> 
> On Tue, Aug 30, 2011 at 12:35 AM, Sonal Goyal <[email protected]> wrote:
> 
> > Hi,
> >
> > Can you please give an example or explain in more detail what you are
> > trying
> > to achieve.
> >
> > Best Regards,
> > Sonal
> > Crux: Reporting for HBase <https://github.com/sonalgoyal/crux>
> > Nube Technologies <http://www.nubetech.co>
> >
> > <http://in.linkedin.com/in/sonalgoyal>
> >
> >
> >
> >
> >
> > On Tue, Aug 30, 2011 at 11:59 AM, highpointe <[email protected]>
> > wrote:
> >
> > > We are attempting to build what is akin to a CRM (but not).
> > >
> > > Our backend is an interface in which clients can control the variables of
> > > their assets offering; the variables of the template they use act as the
> > > over call on the Db.
> > >
> > > Within the UI, they have the ability to set thresholds for variables
> > (once
> > > reached the variable is ejected and in essence a completely new template
> > is
> > > created).
> > >
> > > The variables can change rapidly throughout the day so speed on updates
> > and
> > > being able to always have the latest template data sets on the front end
> > (as
> > > simple search engine) is a priority.
> > >
> > > I have gone through numerous schema in my head but cannot seem to figure
> > > our the automating of the process of expiring data and introducing new
> > > variables on the fly without a complete reindex of the table.
> > >
> > > Any help with architecture ideas would be greatly greatly appreciated.
> > >
> > > Cheers.
> > >
> > > H-p
> > >
> > >
> > >
> > >
> > > Sent from my iPhone
> > >
> >
                                          

Reply via email to