Skip to content

index.md

Latest commit

 

History

History
91 lines (64 loc) · 3.63 KB

index.md

File metadata and controls

91 lines (64 loc) · 3.63 KB

dataset

The documentation is organized around the command line options and as a series of "how to" style examples.

Command line program documentation

  • dataset - usage page for managing collections with dataset

Internal project concepts

dataset Operations

The basic operations support by dataset are listed below organized by collection and JSON document level.

A word about keys

dataset is based around the concept of key/value pairs where the key is the unique identifier for an object stored (i.e. the value) in the collection. Each storage option supported by dataset and its own issues around what things can be called. Keys should be lower case alpha numeric or underscore only. E.g. the pairtree storage relies on the file system to store the JSON objects. Some file systems are not case sensitive, others face challenges with non-alpha numeric filenames.

Collection Level

  • init creates a collection
  • keys list keys of JSON documents in a collection, supports filtering and sorting
  • has-key returns true if key is found in collection, false otherwise
  • count returns the number of documents in a collection, supports filtering for subsets
  • dump export a collection to a JSON lines file
  • load import an collection from a JSON files file.

JSON Document level

  • create a JSON document in a collection
  • read back a JSON document in a collection
  • update a JSON document in a collection
  • delete a JSON document in a collection

JSON Document Attachments

  • attach a file to a JSON document in a collection
  • attachments lists the files attached to a JSON document in a collection
  • retrieve retrieve an attached file associated with a JSON document in a collection
  • prune delete one or more attached files of a JSON document in a collection

datasetd as a web service

New as of version v2 is a web service providing access to dataset collections. This is described in the datasetd documentation page.

datasetd supports the following end points.

Storage engines

In v2 dataset is starting to suport storing your JSON document in a SQL database. Currently three SQL databases can be used to store the JSON documents, SQLite 3 (default engine, used in dataset's test suites), MySQL 8 (minimally tested), Postgres >= 12 (well tested). See storage engines for more details.

Compatibity

Migrating dataset collections between major versions or just different collections can be done using the "dump" and "load" feature. This replaces the old process in early v2 that required you to run a "repair" operation to convert a collection to the current version of dataset.

Example migrating from dataset "data_v2.ds" from v2 to v3 as "data_v3.ds".

dataset3 init data_v3.ds
dataset dump data_v2.ds | dataset3 load data_v3.ds