incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathanael Thompson (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-234) In TDB, namespace data out of sync when dataset not closed properly
Date Fri, 13 Apr 2012 14:01:19 GMT


Nathanael Thompson commented on JENA-234:

No prob, your change fixed the problem with the above repro, thanks.

That said, the db still gets out of sync when I remove the close command all together.  Is
that acceptable?

public static void main(String[] args) { 
Dataset dataset = TDBFactory.createDataset("/AnyEmptyDir"); 
OntModel model = ModelFactory.createOntologyModel(OntModelSpec.OWL_MEM_MINI_RULE_INF, dataset.getDefaultModel());


> 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