Bug 3624 – History cache should be stored in Java DB

Bug 3624 - History cache should be stored in Java DB


Summary:	History cache should be stored in Java DB

Status:	CLOSED FIXED

Product:	opengrok
Component:	scm
Version:	unspecified
Platform:	ANY/Generic All

Importance:	P4 enhancement
Target Milestone:	0.8
Assigned To:	Knut Anders Hatlen
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-09-27 11:14 UTC by Trond Norbye
Modified:	2009-10-24 21:03 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Trond Norbye 2008-09-27 11:14:12 UTC

The history cache is currently stored as xml files on the filesystem. this is a
verbose format, and we duplicate the information a lot. It should be inserted
into a database instead. I say we should target JavaDB first.

Comment 1 Knut Anders Hatlen 2008-09-27 11:22:07 UTC

We should also have bug #3052 in mind when we work out the solution.

Comment 2 Knut Anders Hatlen 2009-10-24 21:03:45 UTC

A cache that stores the history in a Java DB database is in the development
sources and will be included in the 0.8 release, so I'm closing this bug.

Use the -D option when running the indexer in order to enable the Java DB
backend. -j can be used to change the JDBC driver (Java DB client driver is the
default, but the embedded driver is also supported), and -u to specify a custom
database URL.

Incremental update of the history cache (bug #3052) is also supported by the
Java DB-backed cache.