-
Notifications
You must be signed in to change notification settings - Fork 21
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
Optimize findById for partitioned database #221
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
See parent story #214
Acceptance Criteria
findById
, to support query in a partitioned database, connector should parse the provided id: if it's in patternpartitonKey: id
, then invokedb.partitionedFind()
use case 1
findById('fdb2ff86-78c1-47bb-bc63-f239db06c578')
db.find()
use case 2
findById('USA: fdb2ff86-78c1-47bb-bc63-f239db06c578')
partitionedFind()
The text was updated successfully, but these errors were encountered: