[
https://issues.apache.org/jira/browse/DERBY-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562769#action_12562769
]
Daniel John Debrunner commented on DERBY-3351:
----------------------------------------------
Some thinking at a high level would be useful before diving into which packages
are important.
What's the role of the store module? Currently row storage, transaction
locking, transaction durability, ordering, transaction management & indexing
(and maybe others) are all in the store code in derby. Is a different pluggable
store going to provide all of that functionality, or would it be good to make
some of the features re-useable across different stores?
E.g. transaction managerment should probably be pulled above the store.
> Implement a Pluggable Storage Engine Architecture in Derby
> ----------------------------------------------------------
>
> Key: DERBY-3351
> URL: https://issues.apache.org/jira/browse/DERBY-3351
> Project: Derby
> Issue Type: New Feature
> Components: Services, SQL, Store
> Reporter: Dibyendu Majumdar
> Assignee: Dibyendu Majumdar
>
> My aim is to create a pluggable storage engine architecture for Derby, so
> that the default store implementation can be replaced with alternative
> storage engines. I have created my own storage engine which I would like to
> use with Derby's SQL layer, so that is a motivation. But I also think that
> this will benefit the community, and could lead to a pluggable storage engine
> architecture similar to that of MySQL.
> I am not yet sure where the storage engine boundary should lie. I would
> welcome input in this area.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
