npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@planet-a/avsc-zstandard-codec

v1.1.1

Published

A `zstandard` codec for `avsc`

Downloads

63

Readme

Zstandard codec for avsc

Zstandard codec for avsc.

How to install

npm i @planet-a/avsc-zstandard-codec

or

yarn add @planet-a/avsc-zstandard-codec

Example:

import Avro from "avsc";
import {
  createDecoderMixin,
  createEncoderMixin,
  codecName,
} from "@planet-a/avsc-zstandard-codec";

const mySchema = Avro.Type.forSchema({ type: "string" });

{
  // encode
  const fileEncoder = Avro.createFileEncoder("./my.avro", mySchema, {
    codec: codecName,
    codecs: {
      ...Avro.streams.BlockEncoder.defaultCodecs(),
      ...createEncoderMixin(),
    },
  })
    .write("Hello")
    .write("World")
    .end();
  await finished(fileEncoder);
}

{
  // decode
  const fileDecoder = Avro.createFileDecoder("./my.avro", {
    codecs: {
      ...Avro.streams.BlockEncoder.defaultCodecs(),
      ...createDecoderMixin(),
    },
  }).on("data", console.log.bind(console));
  await finished(fileDecoder);
}

Why @mongodb-js/zstd?

It uses the @mongodb-js/zstd package, as this package has a few advantages:

  • The decompress function does not need the uncompressed buffer size in advance, a restriction which most other WASM-based implementations have and renders them unusable for this task
  • It works with Buffer. Whilst a Uint8Array implementation would be more portable (I am looking at you, Deno), [email protected] itself is using Buffer. https://github.com/mtth/avsc/pull/452 has landed, so we might have some more options of what packages to use once we drop [email protected] support.

A note about Snowflake compatibility

You'll see that the current implementation uses defaults from the Avro repository.

Namely:

  • the codec name (if you don't adhere to zstandard the file won't be readable at all)
  • whether to use a checksum or not (with checksum, the metadata will be readable, but the data will yield an error (Could not read file)).

The reason for that is, that in order to make the Avro export as portable as possible, we need to make sure that none of these things need to be specified. A prime example of that is for example Snowflake's Avro support (COPY INTO). Specifically, if you alter the codec name and/or the checksum flag, you won't be able to use the generated Avro files via their product.