You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2013/02/15 17:31:48 UTC
[Apache Bloodhound] #394: Improve index with DB consistency
#394: Improve index with DB consistency
--------------------------+---------------
Reporter: andrej | Owner:
Type: enhancement | Status: new
Priority: major | Version:
Resolution: |
--------------------------+---------------
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/394>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #394: Improve index with DB consistency
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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: <https://issues.apache.org/bloodhound/ticket/394#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #394: Improve index with DB consistency
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#394: Improve index with DB consistency
--------------------------+--------------------------------------
Reporter: andrej | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone: Unscheduled
Component: search | Version:
Resolution: | Keywords: bep-0004 bep-0004-stable
--------------------------+--------------------------------------
Changes (by andrej):
* milestone: Release 6 => Unscheduled
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/394#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #394: Improve index with DB consistency
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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-stable
--------------------------+--------------------------------------
Changes (by andrej):
* keywords: bep-0004 bep-0004-beta => bep-0004 bep-0004-stable
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/394#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker