Suppose I wanted to use this log approach. Does anyone have suggestions about the best way to do it? The approach that first comes to mind is to store the log as a separate DB table, and to maintain that table using a DB trigger attached to the underlying source data table. This is clearly not the only option, though. Perhaps sometimes it would be better to maintain the log as a text file, rather than in the DB. Or perhaps the log should be maintained at the application layer, not the DB layer. Or with a stored procedure, rather than a trigger.
On Jan 16, 2008 9:50 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote: > >> Does anyone have more experience doing [transactional Solr] and whants to share? > > My advice: don't. > > I work with (or work with people who work with) about two dozen Solr > indexes -- we don't attempt to update a single one of them in any sort of > transactional way. ... Some of them are updated in batch (ie: once every N > minutes > code checks a log of all logical objects modified/deleted from the DB and > sends the adds/delets to Solr; ...
