You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
yichen88
changed the title
Inconsistence behavior betweet mapdb and cassandra
Inconsistence behavior between mapdb and cassandra
Feb 11, 2021
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:
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)
The text was updated successfully, but these errors were encountered: