Berkeley DB Feature Survey

Berkeley DB Future Features

 
The Berkeley DB team wants to hear from you!

What follows is a list of potential features that we're considering for future Berkeley DB releases. We'd like your feedback on this list, comments about how you use Berkeley DB and suggestions for additional features that you would like to see in the future. Although we are very interested in hearing your opinion, this survey does not constitute a commitment to implement any of the features listed below.

This survey is specifically for the Berkeley DB product. It is not intended to address features for Berkeley DB XML or Berkeley DB Java Edition. We will have future surveys for those products.

Thank you,

Oracle Berkeley DB Product Management
*
1. The BDB team is considering the following features. For each feature, please indicate the relative importance of that feature for you.

Absolutely Do ThisVery InterestingOKNot Very InterestingDon't Bother
Integration: Oracle Enterprise Manager integration
Integration: Integration with a generic report writer (JDBC, ODBC or ADO.NET). Please specify which report writer(s) would be of particular interested to you in the space provided for Question 2.
Locking: Distributed Lock Manager. Basically this would allow BDB to be stored on a shared disk resource and accessed from multiple systems. Since distributed lock coordination requires additional coordination and overhead, if enabled this feature will impact transaction throughput.
Access Methods: Support database compaction for the HEAP and/or HASH access methods. Please provide details in the space provided for Question 2 about which access method is most important for you.
Access Methods: Add support for API based (non-SQL) triggers on data operations.
Data Management: Add support enabling access of non-SQL data via the SQL API and/or access of SQL data via the key-value API. Please provide details in the space provided for Question 2 about which form of access is most important to you.
Data Management: Add support for automatic data aging (deletion) based on some criteria (time-to-live and/or disk space, for example).
Data Management: Add a schema description layer for non-SQL APIs (key-value, Java collections, Java DPL).
Indexing: Full Text Index search. Add support for full text indices, which may include support for stemming, stop words, regular expressions and wildcard searches.
SQL API: Support for table disk location definition, allowing application to specify where to store data for a given table/database.
SQL API: Support for table partitioning, allowing the application to define partitioning scheme and partition location on disk.
SQL API: Allow writes to BFILE extension. Extend the current BFile extension to allow writes as well as reads.
SQL API: Add ability to specify HEAP or HASH access methods in addition to the default B-Tree support.
SQL API: Add support for multi-row bulk operations.
HA: Add support for multi-master replication.
HA: Add support for write-anywhere replication via write forwarding.
HA: Partial replication. Allow a replica to contain a subset of database tables. A partial replica would support read operations, but would not be able to become a master.
HA: Add notification triggers on the replica. Allow a replicated application to know when certain data changes occur due to replication.
Security: Add an API to support user authentication. Today this is typically handled by the embedding application.
Security: Add an API to provide an audit log, with details beyond what is currently available from the BDB transaction log today.
Security: Add an API to support adding user/operation/object permissions. Today this is typically handled by the embedding application.
General performance and throughput enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2.
General documentation and examples enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2.
Comparative benchmark enhancements. Take an existing comparative benchmark and spend time implementing and/or enhancing the Berkeley DB implementation for that benchmark. Please specify which benchmark(s) are of particular interested to you in the space provided for Question 2.
Powered by SurveyMonkey
Check out our sample surveys and create your own now!