Chris Hostetter wrote: > : I chugg away at 1.5 million records in a single file, but solr never > : commits. specifically, it ignores my <autocommit> settings. (I can > : commit separately at the end, of course :) > > the way the autocommit settings work is soemthing i always get confused by > -- the autocommit logic may not kick in untill the <add> is > finished, regardless of how many docs are in it -- but i'm not certain > 9and if i'm correct, i'm not sure if that's a bug or a feature)
ok, that makes sense. fwiw, I tried to break the records into <add> chunks in the same file but solr complained about multiple root entities. I knew you couldn't mix adds and deletes (rats ;) but I figured multiple add blocks would be ok. I guess not :) > > this may be a motivating reason to use DIH in your use case even though > you've already got it in the XmlUpdateRequestHandler format. yeah, I'll check. though I don't know what I'd do with trying to figure out which records were committed and which weren't... > > : but I might be misunderstanding autocommit. I have it set as the > : default solrconfig.xml does, in the updateHandler section (mapped to > : UpdateHandler2) but /update is mapped to XmlUpdateRequestHandler. > : should I be shuffling some things around? > > due to some unfortunately naming decisions several years ago an "update > Handler" and a "Request handler" that does updates aren't the same thing > ... <updateHandler> (which whould always be DirectUpdateHandler2) is the > low level internal code that is responsible for actually making the index > modiciations -- XmlUpdateRequestHandler (or DataImportHandler) parses the > raw input and hands off to DirectUpdateHandler2 to make the changes. ok, thanks. I kind of implied that from the wiki, but it was still confusing, so thanks for the clarification. --Geoff
