incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (JENA-234) In TDB, namespace data out of sync when dataset not closed properly
Date Fri, 13 Apr 2012 11:37:17 GMT


Andy Seaborne resolved JENA-234.

       Resolution: Fixed
    Fix Version/s: TDB 0.9.1
         Assignee: Andy Seaborne

Fix applied to SVN.  It'll be in the development snapshot build of TDB in an hour or so. 
If you could confirm it's fixed, I'd be grateful.

And thank you for a complete, minimal example.  It makes things a lot easier to find.

> In TDB, namespace data out of sync when dataset not closed properly
> -------------------------------------------------------------------
>                 Key: JENA-234
>                 URL:
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: TDB
>    Affects Versions: TDB 0.9.0
>         Environment: Windows 7.  I think this can be repro'ed in any environment
>            Reporter: Nathanael Thompson
>            Assignee: Andy Seaborne
>             Fix For: TDB 0.9.1
>         Attachments:
> When a TDB model is not closed properly.  the NodeToId table get's out of sync with the
IdToNode table.  This is because writeBuffer in ObjectFileStorage doesn't get written, but
the data in the NodeToId table does get written.  This causes the error mentioned in the following
email thread: 
> Normally I'd say this isn't a bug because the user should close their models correctly.
 But it seems like this should be fixed, because this mistake breaks TDB for all future uses,
and possibly forces the user to recreate the whole db.  I'd be fine with just not writing
the buffered data to both tables, as long as they're in sync.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message