You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2006/12/05 13:16:23 UTC
[jira] Created: (QPID-156) Implement persistence to disk for Qpid
Implement persistence to disk for Qpid
--------------------------------------
Key: QPID-156
URL: http://issues.apache.org/jira/browse/QPID-156
Project: Qpid
Issue Type: New Feature
Components: Java Broker
Affects Versions: M1, M2
Reporter: Marnie McCormack
Priority: Minor
Currently, we only provide an implementation of persistence in-memory using Qpid code. For persistence to disk we use the Berkeley DB. Would be better to offer an alternative imeplmentation which allows the use of Apache licensed code for persistence to disk.
Previously been discussion on dev list regarding best solution for this, including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
More implementation details to be added by assignee please prior to progressing this change.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-156) Implement persistence to disk for Qpid
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-156:
--------------------------------
Fix Version/s: M3
> Implement persistence to disk for Qpid
> --------------------------------------
>
> Key: QPID-156
> URL: https://issues.apache.org/jira/browse/QPID-156
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: M1, M2
> Reporter: Marnie McCormack
> Priority: Minor
> Fix For: M3
>
>
> Currently, we only provide an implementation of persistence in-memory using Qpid code. For persistence to disk we use the Berkeley DB. Would be better to offer an alternative imeplmentation which allows the use of Apache licensed code for persistence to disk.
> Previously been discussion on dev list regarding best solution for this, including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
> More implementation details to be added by assignee please prior to progressing this change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-156) Implement persistence to disk for Qpid
Posted by "Steven Shaw (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-156?page=comments#action_12455616 ]
Steven Shaw commented on QPID-156:
----------------------------------
We could also try ActiveMQ's Kaha store.
Another option is Perst - a low level odbms with store-like interface.
http://www.garret.ru/~knizhnik/java.html
Perst is now developed as a commercial odbms product http://www.mcobject.com/perst/
However the author was kind enought to provide a link to the last release of the code under a friendly licence:
http://www.garret.ru/~knizhnik/perst-249.zip (MIT licence)
At some point it had favorable performance compared to BDB:
http://www.garret.ru/~knizhnik/perstbench.html
After reviewing the design documentation though it looks like multithreaded performance could be an issue:
http://www.garret.ru/~knizhnik/eoodbms.html
Another option is the Consus RDBMS from the same author. It includes a low-level store interface similar to Perst in some ways.
http://www.garret.ru/~knizhnik/consus.html (new BSD licence)
> Implement persistence to disk for Qpid
> --------------------------------------
>
> Key: QPID-156
> URL: http://issues.apache.org/jira/browse/QPID-156
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: M1, M2
> Reporter: Marnie McCormack
> Priority: Minor
>
> Currently, we only provide an implementation of persistence in-memory using Qpid code. For persistence to disk we use the Berkeley DB. Would be better to offer an alternative imeplmentation which allows the use of Apache licensed code for persistence to disk.
> Previously been discussion on dev list regarding best solution for this, including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
> More implementation details to be added by assignee please prior to progressing this change.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-156) Implement persistent store with Apache
compliant licence
Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Greig updated QPID-156:
------------------------------
Description:
Currently, we have no persistent store implementation that can be hosted on Apache due to licence issues. (We use Berkeley DB currently). Would be better to offer an alternative imeplmentation which allows the use of Apache licensed code for persistence to disk.
Previously been discussion on dev list regarding best solution for this, including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
More implementation details to be added by assignee please prior to progressing this change.
was:
Currently, we only provide an implementation of persistence in-memory using Qpid code. For persistence to disk we use the Berkeley DB. Would be better to offer an alternative imeplmentation which allows the use of Apache licensed code for persistence to disk.
Previously been discussion on dev list regarding best solution for this, including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
More implementation details to be added by assignee please prior to progressing this change.
Summary: Implement persistent store with Apache compliant licence (was: Implement persistence to disk for Qpid)
Updated the subject to make it clear that the lack of persistent store was a licence issue.
> Implement persistent store with Apache compliant licence
> --------------------------------------------------------
>
> Key: QPID-156
> URL: https://issues.apache.org/jira/browse/QPID-156
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: M1, M2
> Reporter: Marnie McCormack
> Priority: Minor
> Fix For: M3
>
>
> Currently, we have no persistent store implementation that can be hosted on Apache due to licence issues. (We use Berkeley DB currently). Would be better to offer an alternative imeplmentation which allows the use of Apache licensed code for persistence to disk.
> Previously been discussion on dev list regarding best solution for this, including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
> More implementation details to be added by assignee please prior to progressing this change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-156) Implement persistent store with Apache
compliant licence
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-156.
--------------------------------
Resolution: Fixed
Rob added a Derby store
> Implement persistent store with Apache compliant licence
> --------------------------------------------------------
>
> Key: QPID-156
> URL: https://issues.apache.org/jira/browse/QPID-156
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: M1, M2
> Reporter: Marnie McCormack
> Priority: Minor
> Fix For: M3
>
>
> Currently, we have no persistent store implementation that can be hosted on Apache due to licence issues. (We use Berkeley DB currently). Would be better to offer an alternative imeplmentation which allows the use of Apache licensed code for persistence to disk.
> Previously been discussion on dev list regarding best solution for this, including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
> More implementation details to be added by assignee please prior to progressing this change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.