hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From y_823...@tsmc.com
Subject Re: HBase Design Considerations
Date Mon, 03 May 2010 06:55:30 GMT
You should also consider about some  aggregate function in oracle, these
handy functions like
Max , Min, Count, ROWNUM=1 etc... we used to use it well in oracle,
but it will be very difficult or inefficient to do the some function in
Hbase.

Fleming Chiu(邱宏明)
707-6128
y_823910@tsmc.com
週一無肉日吃素救地球(Meat Free Monday Taiwan)




|---------+----------------------------->
|         |           Saajan            |
|         |           <ssangraula@verisk|
|         |           health.com>       |
|         |                             |
|         |           2010/05/03 02:42  |
|         |           PM                |
|         |           Please respond to |
|         |           hbase-user        |
|         |                             |
|---------+----------------------------->
  >-------------------------------------------------------------------------------------------------------------|
  |                                                                                      
                      |
  |       To:      hbase-user@hadoop.apache.org                                          
                      |
  |       cc:      (bcc: Y_823910/TSMC)                                                  
                      |
  |       Subject: HBase Design Considerations                                           
                      |
  >-------------------------------------------------------------------------------------------------------------|





We are working on a prototype to migrate our healthcare database, currently
in Oracle, to HBase.
Our java based web application allows end users to search patients on over
50 different criteria through a query builder interface: typical queries
involve identifying members who match filter conditions on diagnosis,
procedures, doctors and hospitals, time intervals, employer and so forth.
The database has records for over 5 million patients for a number of years,
and is around 10 TB in size.
A major design issue we are facing is to allow fast querying in HBase with
so many searchable columns. We are experimenting with secondary index
tables, multiple tables etc., but haven't been able to reach a conclusion
on
the way ahead. Expected user response time is up to 4 seconds.

Would highly appreciate comments on how HBase is used to support search
applications and how we can support search / filter across multiple
criteria
in HBase.

Thanks
Saajan
--
View this message in context:
http://old.nabble.com/HBase-Design-Considerations-tp28431975p28431975.html
Sent from the HBase User mailing list archive at Nabble.com.





 --------------------------------------------------------------------------- 
                                                         TSMC PROPERTY       
 This email communication (and any attachments) is proprietary information   
 for the sole use of its                                                     
 intended recipient. Any unauthorized review, use or distribution by anyone  
 other than the intended                                                     
 recipient is strictly prohibited.  If you are not the intended recipient,   
 please notify the sender by                                                 
 replying to this email, and then delete this email and any copies of it     
 immediately. Thank you.                                                     
 --------------------------------------------------------------------------- 




Mime
View raw message