Revert previous changes from https://github.com/vaticle/typedb-client-nodejs/pull/202, which made query queues and iterators throw the same error idempotently. However, this goes counter to standard usage of iterators and queues, which are not meant to behave idempotently (each item is only returned once, and if they have an error they should no longer be used).
What are the changes implemented in this PR?
remove idempotent error state of collectors and queues, which back query iterators
note that we still store the error on the transaction bidirectional stream, in case the server throws an exception when there are no query iterators active
What is the goal of this PR?
Revert previous changes from https://github.com/vaticle/typedb-client-nodejs/pull/202, which made query queues and iterators throw the same error idempotently. However, this goes counter to standard usage of iterators and queues, which are not meant to behave idempotently (each item is only returned once, and if they have an error they should no longer be used).
What are the changes implemented in this PR?
Note: mirrors change from https://github.com/vaticle/typedb-client-java/pull/372