Hi, For integrating HBase and Apache Solr (or any other indexing/search platform) we came up with Smart CMS [1][2]. We are on the verge of releasing its 0.1 version which is actually production ready and will be used in production straight away. Smart CMS was designed and developed with a goal of uniting concepts of Objects with (HBase + Solr). IOW, we will design objects, and Smart CMS will take care of persisting it and making it available for search. Though initially we have chosen Apache Solr as the search engine but it is very easy to plugin any other search engine of our choice, since we expose the integration of search functionality through SPI.
A little bit of history of how we came into developing it and what it is currently being used for. We started the development of it as we needed a flexible content management system for an e-Commerce Platform as a Service of ours. As we engrossed ourselves into it we found 'content' to be synonymous to 'Object' in OOP paradigm and we started development around it. As a result now we have a system that can be used both as a traditional Content Management System and as a Content Repository. We used it in as a traditional CMS capacity to manage Pages for the partner websites for our e-Commerce PaaS; i.e. customers can create pages for - product, promotion, store, etc. manage page contents for front page, category page; links associated products, related products etc from UI where the UI is dynamically generated using the content definitions. We also used the CMS for extensive search functionalities such as, full text search, facet search, range search, auto completion etc. For this we access the CMS using its Web Service library, we use Solr directly for advance searches and to access both of them we use a tag library. The flexibility Smart CMS provided us in fact helped us win 2 big customers. We used CMS as a content repository where Smart CMS is actually being used to generate domain/dto, data access layer codes for API/Service layers to use them to persist Java POJOs; i.e.users of it defines a XML we call 'Content Type Definition'. A content type definition is synonymous to an Object Diagram; where we define objects, their inheritance and compositions. This code generation is an approach we took to bypass Java Reflection API and it is done by a Maven Plugin we have written. We have another plugin which helps us start all CMS related applications within Maven so that we can write integration tests on the fly. An example of repository mode is available in our Application Smart Email Queue [3], which is designed to send emails from our PaaS. After proving sustainable performance in this mode, Smart CMS has also been chosen for 4G Telecom Application Server project's database. [1] Smart CMS - http://smart-cms.org [2] Smart CMS Source - https://github.com/SmartITEngineering/smart-cms [3] Smart Email Queue Source - https://github.com/SmartITEngineering/smart-email-queue We would welcome any feedback, criticism, involvement in Smart CMS. If you have any further queries please feel free to ask them. Thank you, Imran On Sat, Mar 10, 2012 at 8:41 PM, Gopal <[email protected]> wrote: > On 03/08/2012 11:56 AM, Stack wrote: >> >> On Thu, Mar 8, 2012 at 12:18 AM, Mohammad Tariq<[email protected]> >> wrote: >> >>> >>> Hello list, >>> >>> We are planning to index our data stored in HBase using Solr.As we >>> are totally new to Solr, we would like to have some comments from >>> someone who is already doing it..While looking over the internet we >>> came across Liliy.Is there any other other option, or Lily is the only >>> preferable way??Many thanks. >>> >>> >> >> You should spend time evaluating lily. The lads have been working on >> the solr+hbase union for a good while now. >> >> There is also https://github.com/Photobucket/Solbase that you might >> take a look at. >> >> And yes, of course, there is ES (We're partial because we work w/ >> Shay). Let us know if you make progress w/ the latter. >> >> Yours, >> St.Ack >> > > Lily is great. However as a front end tool , do you know if we have to > depend on another front end tool provider such as Pentaho to leverage the > full potential of Lily. > > Lily is definitely extremely promising. I was able to run their test lily > server > comprising of Hadoop, Hbase, Solr and Lily right off the box. > > Extremely small footprint and runs as given in their website. However the > issue I am having is that it does not have a Front end to go along with it. > > It is definitely very very promising technology . > Thanks -- Imran M Yousuf Entrepreneur & CEO Smart IT Engineering Ltd. Dhaka, Bangladesh Twitter: @imyousuf - http://twitter.com/imyousuf Blog: http://imyousuf-tech.blogs.smartitengineering.com/ Mobile: +880-1711402557
