incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #394: Improve index with DB consistency
Date Fri, 15 Feb 2013 16:32:46 GMT
#394: Improve index with DB consistency
  Reporter:  andrej       |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:  Release 6
 Component:  search       |    Version:
Resolution:               |   Keywords:  bep-0004 bep-0004-beta
Changes (by andrej):

 * owner:   => nobody
 * keywords:   => bep-0004 bep-0004-beta
 * component:   => search
 * milestone:   => Release 6

Old description:

New description:

 * Current implementation uses ITicketChangeListener interface that is
 triggered after DB transaction is already committed. There is possiblity
 to get inconsistency between DB and search index if index update fails. In
 this case reindex is required. One of the possible solution is to contact
 Trac community with suggestion to introduce a new, within transaction,
 I<Resource>ChangingListener interface. During this event we can save
 changes into additional table and than index changes in separate thread.
    * Some ticket changes are not reflected in event interfaces e.g.
 Version and Component renaming. One of the possible solution is to contact
 Trac community to introduce new interfaces.
    * Alternative solution is triggering events from SQL proxy developed on
 multi-product branch
    * Usage of DB triggers is another alternative


Ticket URL: <>
Apache Bloodhound <>
The Apache Bloodhound (incubating) issue tracker

View raw message