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

Invalid keyspaces when using lagom:runAll in Maven with unmanaged Cassandra #476

Closed
ignasi35 opened this issue Feb 15, 2017 · 0 comments
Closed
Assignees
Milestone

Comments

@ignasi35
Copy link
Contributor

ignasi35 commented Feb 15, 2017

Lagom's DevMode should create one Cassandra keyspace per service. When running a maven project with an unmanaged Cassandra (external) Lagom doesn't create one keyspace per service but three keyspaces:

  • lagom: contains tables config, messages and metadata
  • lagom_snapshot: contains table snapshots
  • lagom_reads: contains table offsetstore and other user-defined tables. This keyspace is only created if a read-side is used in the project.

Expected:

One keyspace per service is created and it contains all the tables for that specific service.

Extra details:

Using Lagom 1.2.2 the following scenarios where tested:

  • sbt + embedded cassandra: one keyspace per service
  • sbt + external cassandra: one keyspace per service
  • mvn + embedded cassandra: one keyspace per service
  • mvn + external cassandra: several keyspaces
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants