Errors with partitioning by callback or keys (JNI/Java), bug?

Question

Hello,
Just upgraded to 4.8, to test new partitioning features. Seems to be not working for me, or maybe I'm doing something wrong?
Vista 64-bit, Java 1.6.0_16 32-bit, BDB 4.8.24 32-bit.
Callback-based partitioning:
public class InfoDataPartitionHandler implements PartitionHandler {
@Override
public int partition(Database db, DatabaseEntry key) {
     return 0; // just testing
DatabaseConfig cfg = new DatabaseConfig();
cfg.setAllowCreate(true);
cfg.setPartitionByCallback(4, new InfoDataPartitionHandler());
cfg.setType(DatabaseType.BTREE);
Database db = env.openDatabase(null,"test",null,cfg);
And this is what I get when running, looks like a bug actually:
Exception in thread "main" java.lang.IllegalArgumentException: DatabaseEntry must not be null
at com.sleepycat.db.internal.db_javaJNI.Db_set_partition(Native Method)
at com.sleepycat.db.internal.Db.set_partition(Db.java:497)
at com.sleepycat.db.DatabaseConfig.configureDatabase(DatabaseConfig.java:2206)
at com.sleepycat.db.DatabaseConfig.openDatabase(DatabaseConfig.java:2105)
at com.sleepycat.db.Environment.openDatabase(Environment.java:314)
Key-based partitioning
Things are even worse.
DatabaseEntry k1 = new DatabaseEntry();
StringBinding.stringToEntry("111111111111111111111111", k1);
int sz = k1.getSize();
MultipleDataEntry keys = new MultipleDataEntry(new byte[sz]);
keys.append(k1);
DatabaseConfig cfg = new DatabaseConfig();
cfg.setAllowCreate(true);
cfg.setPartitionByRange(2, keys);
cfg.setType(DatabaseType.BTREE);
Database db = new Database("/tmp/test.db", null, cfg);
db.close();
Exception in thread "main" com.sleepycat.db.DatabaseException: DB_NOTFOUND: No matching key/data pair found: DB_NOTFOUND: No matching key/data pair found
at com.sleepycat.db.internal.db_javaJNI.Db_open(Native Method)
at com.sleepycat.db.internal.Db.open(Db.java:449)
at com.sleepycat.db.DatabaseConfig.openDatabase(DatabaseConfig.java:2106)
at com.sleepycat.db.Database.<init>(Database.java:103)
at Temp.main(Temp.java:23)
Please help.

Answer 1

Hello. Thanks for this report, both situations you've reported are bugs in Berkeley DB. We are currently validating patches internally.
Please contact me directly at ben dot schmeckpeper at the obvious domain.
Thanks,
Ben