<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="-1"><font face="DejaVu Sans Mono">Hello all,<br>
<br>
<font size="-1">Thanks to </font></font></font><small><font
face="DejaVu Sans Mono">Arkadiusz Miskiewicz for sharing his
knowledge here:<br>
<br>
<a class="moz-txt-link-freetext" href="http://lists.fsck.com/pipermail/rt-users/2011-August/072464.html">http://lists.fsck.com/pipermail/rt-users/2011-August/072464.html</a><br>
<br>
My question is based exactly on this config which I find is good.<br>
<br>
"As per my understanding" the 'delta' index makes newly created
<br>
rows/records available by using '</font><font face="DejaVu Sans
Mono">SphinxCounters' table. That is<br>
the delta index which will be run every 15 minutes will check if<br>
any row which has 'id' greater than the 'id' stored previously <br>
</font><font face="DejaVu Sans Mono">in 'max_doc_id' column of </font></small><small><font
face="DejaVu Sans Mono">'</font><font face="DejaVu Sans Mono">SphinxCounters'
table. If greater<br>
then it will read the source and then add the new record to the
<br>
'delta' index. <br>
<br>
</font></small><br>
<small><font face="DejaVu Sans Mono">If an edit/update happens to an
<b>"existing"</b> ticket/document/row in <br>
the source database, how will this change get updated into indexes<br>
quickly? So according to this config, we will need to wait until<br>
the next time the 'main' is reindexed again, right? If true how
<br>
can we have a workaround for this problem?<br>
<br>
Please excuse and let me know if I made any wrong assumptions<br>
here.<br>
<br>
Thanks,<br>
</font></small>
</body>
</html>