Giter VIP home page Giter VIP logo

json-depth-stream's Introduction

json-depth-stream

NPM version Build Status

Why?

It is impossible to parse 1gb JSON file with native node.js primitives.

How?

Just a streaming parser, nothing really fancy. The only difference between this parser and the others is that it can skip data that is nested too deeply.

Installation

npm install json-depth-stream

Usage

const DepthStream = require('json-depth-stream');

const file = require('fs').createReadStream('/tmp/big.json');
const json = new DepthStream(1 /* desired depth */);

json.on('visit', (path, start, end) => {
  // `path` is a nested JSON key like: `["a", 0, "b"]`, which is equivalent to
  // `obj.a[0].b` (assuming `obj.a` is an Array)

  // `start` and `end` are offsets in the input stream
  // they could be used in `fs.read()` if streaming from file.
  console.log(path, start, end);
});

file.pipe(json);

Query:

const json = new DepthStream(1);

const q = json.query([ 'path' ]);
q.pipe(process.stdout);
q.once('end', () => {
  process.stdin.unpipe(json);
});

process.stdin.pipe(json);

Stream-once usage:

const json = new DepthStream(1);

process.stdin.on('data', (chunk) => {
  json.update(chunk);
});

// `split` event is emitted when parser enters new object value/array element.
// `index` is local to `chunk`.
json.on('split', (path, index) => {
  // `path` is the same as above
  // `index` is an index in a `chunk` that was given to `.update(chunk)`
  console.log(path, index);
});

Speed

Around 100mb/s for JSON with many object keys, faster for array-like JSONs:

$ node benchmark/throughput.js
Throughput: 100.00 mb/s

LICENSE

This software is licensed under the MIT License.

Copyright Fedor Indutny, 2020.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

json-depth-stream's People

Contributors

indutny avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

caitoulin

json-depth-stream's Issues

Is there an any key?

I'd like to query @ 3-levels deep, returning every key with a path like users/${uid}/firstName

I've tried true and '*', but no dice

Parsing a stream of concatenated JSON documents

I'm trying to parse a stream of concatenated JSON documents like

{"x":"y"}{"x":"y"}{"x":"y"}

Is there some way to get an event at the boundaries between JSON documents, so I could process each separately?

How to associate chunks and offsets?

I'm interested in streaming JSON from a web service to transform array items as they arrive over the wire. I love that this parser can handle depth, because I would not necessarily like to parse each individual array item. I just want to get a hold of the string/buffer of each individual (parse-able but not parsed) array item. This library appears to provide offsets but there's no obvious way to get at the chunks themselves or, for example, to know which chunks the offsets provided by split refer to.

To achieve what I'm talking about, is it safe to use the explicit stream-once usage and assume that when update(chunk) is called, split/visit events will be fired synchronously, all for the data in chunk?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.