Proposal
Can we add support to the nsFrom/nsTo options on the PerconaServerMongoDBRestore.
This is already supported by the Pbm agent itself as described here but the operator itself does not allow to use them as confirmed here
Allow something similar to the following:
selective:
nsFrom: "<DATABASE.ORIGINAL_COLLECTION_NAME>"
nsTo: "<DATABASE.NEW_COLLECTION_NAME>"
Use-Case
When you need to do a partial recover of a database, because you had run a bad delete where certain condition was true. We need to restore just the data you delete by mistake.
Pbm don't support partial restores based on query either. So you need to restore to a new collection, and eventually validate and merge into the original using an aggregation.
If we use the operator, would be good if all operation could be done from the operator, without the need for the CLI or ssh into the pods.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
Proposal
Can we add support to the nsFrom/nsTo options on the PerconaServerMongoDBRestore.
This is already supported by the Pbm agent itself as described here but the operator itself does not allow to use them as confirmed here
Allow something similar to the following:
Use-Case
When you need to do a partial recover of a database, because you had run a bad delete where certain condition was true. We need to restore just the data you delete by mistake.
Pbm don't support partial restores based on query either. So you need to restore to a new collection, and eventually validate and merge into the original using an aggregation.
If we use the operator, would be good if all operation could be done from the operator, without the need for the CLI or ssh into the pods.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response