lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Resolved: (LUCENE-1149) add XA transaction support
Date Mon, 22 Sep 2008 18:58:44 GMT


Michael McCandless resolved LUCENE-1149.

    Resolution: Duplicate

I believe LUCENE-1274 (separation of prepareCommit & commit) already provides the low
level support for building XA transactions on top of Lucene?

> add XA transaction support
> --------------------------
>                 Key: LUCENE-1149
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Index
>            Reporter: robert engels
> Need to add XA transaction support to Lucene.
> Without XA support, it is difficult to keep disparate resources (e.g. database) in sync
with the Lucene index.
> A review of the XA support added to Hibernate might be a good start (although Hibernate
almost always uses a XA capable backing store database).
> It would be ideal to have a combined IndexReaderWriter instance, then create a XAIndexReaderWriter
which wraps it.
> The implementation might be as simple as a XA log file which lists the XA transaction
id, and the segments XXX number(s), since Lucene already allows you to rollback to a previous
version (??? for sure, or does it only allow you to abort the current commit).
> If operating under a XA transaction, the no explicit commits or rollbacks should be allowed
on the instance.
> The index would be committed during XA prepare(), and then if needed rolledback when
requested. The XA commit() would be a no-op.
> There is a lot more to this but this should get the ball rolling.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message