Open eljefedelrodeodeljefe opened 6 years ago
@eljefedelrodeodeljefe to my knowledge a transform stream is only an interim state in the streaming pipeline. The stream must be consumed somewhere for you to receive the end event. This could be either a piped writable or just a simple .on('data'..) listener. It's not a bug in this library
Hi,
I am struggling to see, why the below test would not work. Maybe I get something wrong. But right now I assume there is something very quirky during the Stream Implementation happening. Maybe some vents won't be passed.
In any case the need to piping to a writable a to get the end event is somehow weird.
I am running on Node 8.
The use case here would be to have an array of query and recursively querying them. I am creating new instances of the client and streams wherever possible.
any help appreciated.