You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2014/11/08 17:40:34 UTC

[jira] [Commented] (JENA-782) Provide configurability of TDB in database setup

    [ https://issues.apache.org/jira/browse/JENA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203493#comment-14203493 ] 

Andy Seaborne commented on JENA-782:
------------------------------------

commit 4a45e361739bd2c8e2df56a9bc02015728b011bf

This merges into master the changes for configurable TDB databases.

Not yet completed: Changes to application API TDBFactory. Currently, an application needs to create database using StoreConnection, then get it via TDBFactory.  This is only to limit the visibility of changes pending detailed testing and usage in TDB and Fuseki. By default, the system should behave exactly as it did before.



> Provide configurability of TDB in database setup
> ------------------------------------------------
>
>                 Key: JENA-782
>                 URL: https://issues.apache.org/jira/browse/JENA-782
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: TDB
>    Affects Versions: Jena 2.12.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>
> Creating TDB databases and attaching to existsing ones is quite fixed currently.   Any internal paramaters are quite difficult to manipulate and they are globals.
> Configurability of TDB databases has two dimensions:
> # Initial setup (e.g. block size)
> # Per JVM (e.g. cache sizes).
> (The file mode is actually a per JVM feature but should probably be regarded as an initial setup feature only.)
> With configurability, TDB and Fuseki could be scaled down for small databases and for many small databases in one JVM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)