jankotek / jankotek/mapdb

What happened to asyncWriteEnable()

Open
#976 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
5.1k
Forks
877
PR merge metrics
No merged PRs in 30d

Description

Hi,

I'm starting out with MapDB. Looks great so far. I'm trying to optimize performance but the docs are confusing.

Here it says to call .asyncWriteEnable() - but that method doesn't exist in MapDB 3.0.8.

Also, the same page says to enable "instance cache", but I can't find that option either.

Please advise!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked performance page and compare its asyncWriteEnable() and instance-cache guidance against the MapDB 3.0.8 API and documentation. Done means the page accurately describes options available in that version or clearly explains their replacements and limitations.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
database, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.