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

Inconsistence behavior between mapdb and cassandra #72

Open
yichen88 opened this issue Feb 11, 2021 · 0 comments
Open

Inconsistence behavior between mapdb and cassandra #72

yichen88 opened this issue Feb 11, 2021 · 0 comments

Comments

@yichen88
Copy link
Contributor

  • Do you want to request a feature or report a bug?

  • What is the current behavior?
    For most getFoo(String nodeId) methods:
    in mapdb, it checks existence and throws exception if not exists
    but in cassandra, it only check nodeId uuid's formats. And return un empty collections if node not found.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • PowSyBl Version: ...
    • OS Version: ...
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)

(if a question doesn't apply, you can delete it)

@yichen88 yichen88 changed the title Inconsistence behavior betweet mapdb and cassandra Inconsistence behavior between mapdb and cassandra Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant