Support streaming results / incrementally adding rows

[automattic]

Support streaming results / incrementally adding rows

[ewnd9]

Did you consider something like below?

stream.on('data', function(data) {
  table.push(data);
  var curr = table.toString().split('\n');
  console.log(curr.slice(prev.length, curr.length).join('\n'));
  prev = curr;
});

[gajus]

@ewnd9 approach seems correct. In addition, consider using something like https://github.com/trentm/node-bunyan, which is designed for handling streams (although output is not in a tabular format).

[glennblock]

You think splitting a large table over and over is a good solution? That
seems pretty expensive especially for a large table.

On Tue, Aug 18, 2015 at 10:34 PM ewnd9 [email protected] wrote:

Did you consider something like below?

stream.on('data', function(data) {
table.push(data);
var curr = table.toString().split('\n');
console.log(curr.slice(prev.length, curr.length).join('\n'));
prev = curr;
});

—
Reply to this email directly or view it on GitHub
#78 (comment)
.

[glennblock]

Thanks for the tip regardless :-)
On Tue, Sep 15, 2015 at 1:29 PM Glenn Block [email protected] wrote:

You think splitting a large table over and over is a good solution? That
seems pretty expensive especially for a large table.

On Tue, Aug 18, 2015 at 10:34 PM ewnd9 [email protected] wrote:

Did you consider something like below?

stream.on('data', function(data) {
table.push(data);
var curr = table.toString().split('\n');
console.log(curr.slice(prev.length, curr.length).join('\n'));
prev = curr;
});

—
Reply to this email directly or view it on GitHub
#78 (comment)
.

[ewnd9]

@glennblock hard to say without benchmarks. You could always implement something like table rotation on every n-th chunk of stream in case of low perfomance

[gajus]

Sorry, I have actually misread the example. You don't need to render the entire table every time. A lot simpler would be to simply render a single row. I am sure cli-table or cli-table2 supports that. If not, have a look at https://www.npmjs.com/package/table.

[glennblock]

@ewnd9 yeah I am just imagining the scenario where one is streaming tons and tons of events. It seems completely wasteful and slow to have an infinitely growing / continually string concatenated table.