lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "DataImportHandlerDeltaQueryViaFullImport" by DanielRijkhof
Date Wed, 20 Jul 2011 12:27:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "DataImportHandlerDeltaQueryViaFullImport" page has been changed by DanielRijkhof:
http://wiki.apache.org/solr/DataImportHandlerDeltaQueryViaFullImport?action=diff&rev1=3&rev2=4

  }}}
  When doing a normal full import solr defaults the {{{clean}}} to {{{true}}} (watch out you
can override this default in the solrconfig.xml so you might want to always set it explicitly
to true). As a result the first part of the WHERE condition will be {{{'true' != 'false'}}}
which any decent RDBMS will figure out will lead to the entire all always evaluating to true
aka reading the entire table: {{{http://localhost:8983/solr/core0/dataimport?command=full-import&clean=true}}}
  
- Now when doing a delta import you do not use the delta import, but instead you do a normal
full-import but with the {{{clear}}} GET parameter set to {{{false}}}: {{{http://localhost:8983/solr/core0/dataimport?command=full-import&clean=false}}}
+ Now when doing a delta import you do not use the delta import, but instead you do a normal
full-import but with the {{{clean}}} GET parameter set to {{{false}}}: {{{http://localhost:8983/solr/core0/dataimport?command=full-import&clean=false}}}
  
  In this case the first part of the WHERE will be {{{'false' != 'false'}}} which is obviously
always false and any RDBMS should optimize that away and just evaluate the second condition.
  

Mime
View raw message