Skip to main content

Home/ Groups/ myRIZZEBookmarks
JE ORFEVRE

BI with MapReduce « Sanjay Sharma's Weblog - 1 views

  •  
    "Pentaho "
JE ORFEVRE

MySQL in Amazon EC2 - Beginners Guide - DatabaseJournal.com - 0 views

    • JE ORFEVRE
       
      toto
    • JE ORFEVRE
       
      test
JE ORFEVRE

mysql - When to consider Solr - Stack Overflow - 0 views

  • will deal entirely with Solr as an example for several search engines that function roughly the same way.
  • Solr/Lucene provides mind blowing text-analysis /
  •  
    "This question calls for a very broad answer to be answered in all aspects. There are very well certain specificas that may make one system superior to another for a special use case, but I want to cover the basics here. I will deal entirely with Solr as an example for several search engines that function roughly the same way. I want to start with some hard facts: You cannot rely on Solr/Lucene as a secure database. There are a list of facts why but they mostly consist of missing recovery options, lack of acid transactions, possible complications etc. If you decide to use solr, you need to populate your index from another source like an SQL table. In fact solr is perfect for storing documents that include data from several tables and relations, that would otherwise requrie complex joins to be constructed. Solr/Lucene provides mind blowing text-analysis / stemming / full text search scoring / fuzziness functions. Things you just can not do with MySql. In fact full text search in MySql is limited to MyIsam and scoring is very trivial and limited. Weighting fields, boosting documents on certain metrics, score results based on phrase proximity, matching accurazy etc is very hard work to almost impossible. In Solr/Lucene you have documents. You cannot really store relations and process. Well you can of course index the keys of other documents inside a multivalued field of some document so this way you can actually store 1:n relations and do it both ways to get n:n, but its data overhead. Don't get me wrong, its perfectily fine and efficient for a lot of purposes (for example for some product catalog where you want to store the distributors for products and you want to search only parts that are available at certain distributors or something). But you reach the end of possibilities with HAS / HAS NOT. You can almonst not do something like "get all products that are available at at least 3 distributors". Solr/Lucene has very nice facetting features and post search an
JE ORFEVRE

Setting Up SOLR on EC2, Part II - The Intellog Blog - It's time for a little intelligen... - 1 views

  •  
    " Therefore, it's not well suited to the storage of SOLR index information, assuming the index data is updated more-or-less constantly."
« First ‹ Previous 101 - 112 of 112
Showing 20 items per page