You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From OrientJS v.3 the returns of a query is a NodeJS streams, in order to support the new pagination feature of OrientDB 3.0.x. So it is possible to pause a stream and resume it later in time.
letstream=session.query("select from OUser",{pageSize: 1})stream.on("data",console.log);stream.pause();setTimeout(()=>{stream.resume();},1000)
This works fine, but still OrientJS, will request for the next page, if available, even if the stream is paused, that can result in high memory footprint due the records being cached in the stream buffer while the stream is in paused state.
OrientJS should not ask for the next page if the stream is paused.
The text was updated successfully, but these errors were encountered:
From OrientJS v.3 the returns of a query is a NodeJS streams, in order to support the new pagination feature of OrientDB 3.0.x. So it is possible to pause a stream and resume it later in time.
This works fine, but still OrientJS, will request for the next page, if available, even if the stream is paused, that can result in high memory footprint due the records being cached in the stream buffer while the stream is in paused state.
OrientJS should not ask for the next page if the stream is paused.
The text was updated successfully, but these errors were encountered: