Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Establish a clear hierarchy of properties and corresponding files #177

Open
asarkar opened this issue Dec 11, 2017 · 1 comment
Open

Establish a clear hierarchy of properties and corresponding files #177

asarkar opened this issue Dec 11, 2017 · 1 comment

Comments

@asarkar
Copy link

asarkar commented Dec 11, 2017

Perhaps it's because I'm new to Akka Persistence, but I'm finding it very difficult to track the zillions of seemingly unrelated properties and where to put them. Some start with akka.contrib.persistence.mongodb, other akka-contrib-mongodb-persistence, and yet another akka.persistence. The documentation, unfortunately, doesn't make it any easier. For example, I wanted to disable snapshots, but the doc only shows how to do it for multiple configurations, which I assume has to be less common than disabling it globally for developmental purposes.

I propose that the doc clearly lays out the properties in a hierarchical manner instead of spreading them all over the place. For a seasoned Akka dev, this may not be much of an issue, but for beginners, this is beyond frustrating. The suggested format is as below:

application.conf

akka {
  contrib {
    persistence.mongodb {
      mongo {
        mongouri # this is the connection URI
        journal-collection # this is the collection name where the events are stored
      }
    }
  }
}

reference.conf

akka {
  persistence {
    journal {
      plugin = "akka-contrib-mongodb-persistence-journal"
    }
  }
}

I believe if the above format is followed, then most of the verbiage in the doc will not be necessary.

@scullxbones
Copy link
Owner

Hi @asarkar -

There was something like this (the default configuration) in the docs as of the 0.x version. I got rid of it for the 1.x version. I think it could be reintroduced - broken up by section with accompanying docs, no problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants