Andy Seaborne created JENA-485:
----------------------------------
Summary: TDB should provide a way to flush journalled data back to
the DB.
Key: JENA-485
URL: https://issues.apache.org/jira/browse/JENA-485
Project: Apache Jena
Issue Type: Bug
Components: TDB
Affects Versions: Jena 2.10.1
Reporter: Andy Seaborne
Priority: Minor
TDB batches write-commits for performance reasons. Commits are safe when they
are flushed to the journal. At some point, the journal is written back to the
main database. This happens periodically in use and always happens on startup.
It would be convenient to allow application code to cleanly force writing the
journal back to the database for the case when the application has been
preparing a database for moving elsewhere. It is not critical the journal is
flushed (its safe anyway) but it is neater for preparing databases for moving
to a server for publication).
Workaround 1 : Set the TransactionManager.QueueBatchSize to zero to make each
write-commit attempt to flush the journal. It may not be able to due to
outstanding read transactions.
Workaround 2 : run any TDB command line tool on the database e.g.
{noformat}
tdbquery --loc=DIR 'ASK{}'
{noformat}
as this will open the database and so flush the journal).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
