Skip to content

missing initialization options from classic-level #14

@maxlath

Description

@maxlath

The possibility to pass initialization options has been removed in 87d54b3, because, if I get it right, those had no effect on follower instances. But they still had an effect on the leader db instantiated with ClassicLevel, so why not leaving that possibility? I'm trying to set maxOpenFiles and cacheSize, but the current implementation doesn't allow it. I'm considering just recovering passing the whole options to the leader db initializer (via this[kOptions]), should I expect any downside to that?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions