IdempotentStorageManager and its integration with FileSplitter

How is the operator using this NoOp implementation supposed to behave? Will the operator not recover at all or will it recover in non-idempotent manner? Can idempotency and the connected overhead be turned off when the application does not require it or will it result in complete loss of recovery?