Downloads of v 5.10.0:


Last Update:

30 Nov 2020

Package Maintainer(s):

Software Author(s):

  • John Kerl


cli cross-platform data foss


  • 1
  • 2
  • 3

5.10.0 | Updated: 30 Nov 2020



Downloads of v 5.10.0:



Software Author(s):

  • John Kerl

  • 1
  • 2
  • 3
Miller 5.10.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install Miller, run the following command from the command line or from PowerShell:


To upgrade Miller, run the following command from the command line or from PowerShell:


To uninstall Miller, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade miller -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade miller -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure miller installed
    name: miller
    state: present
    version: 5.10.0
    source: STEP 3 URL

See docs at

chocolatey_package 'miller' do
  action    :install
  version  '5.10.0'
  source   'STEP 3 URL'

See docs at

    Name: miller,
    Version: 5.10.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller miller
   Name     = 'miller'
   Ensure   = 'Present'
   Version  = '5.10.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'miller':
  provider => 'chocolatey',
  ensure   => '5.10.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install miller version="5.10.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 30 Nov 2020.


Miller is like awk, sed, cut, join, and sort for name-indexed data such as CSV, TSV, and tabular JSON. You get to work with your data using named fields, without needing to count positional column indices.

This is something the Unix toolkit always could have done, and arguably always should have done. It operates on key-value-pair data while the familiar Unix tools operate on integer-indexed fields: if the natural data structure for the latter is the array, then Miller’s natural data structure is the insertion-ordered hash map. This encompasses a variety of data formats, including but not limited to the familiar CSV, TSV, and JSON. (Miller can handle positionally-indexed data as a special case.)


  • Miller is multi-purpose: it’s useful for data cleaning, data reduction, statistical reporting, devops, system administration, log-file processing, format conversion, and database-query post-processing.
  • You can use Miller to snarf and munge log-file data, including selecting out relevant substreams, then produce CSV format and load that into all-in-memory/data-frame utilities for further statistical and/or graphical processing.
  • Miller complements data-analysis tools such as R, pandas, etc.: you can use Miller to clean and prepare your data. While you can do basic statistics entirely in Miller, its streaming-data feature and single-pass algorithms enable you to reduce very large data sets.
  • Miller complements SQL databases: you can slice, dice, and reformat data on the client side on its way into or out of a database. (Examples here and here). You can also reap some of the benefits of databases for quick, setup-free one-off tasks when you just need to query some data in disk files in a hurry.
  • Miller also goes beyond the classic Unix tools by stepping fully into our modern, no-SQL world: its essential record-heterogeneity property allows Miller to operate on data where records with different schema (field names) are interleaved.
  • Miller is streaming: most operations need only a single record in memory at a time, rather than ingesting all input before producing any output. For those operations which require deeper retention (sort, tac, stats1), Miller retains only as much data as needed. This means that whenever functionally possible, you can operate on files which are larger than your system’s available RAM, and you can use Miller in tail -f contexts.
  • Miller is pipe-friendly and interoperates with the Unix toolkit
    Miller’s I/O formats include tabular pretty-printing, positionally indexed (Unix-toolkit style), CSV, JSON, and others
  • Miller does conversion between formats
    Miller’s processing is format-aware: e.g. CSV sort and tac keep header lines first
  • Miller has high-throughput performance on par with the Unix toolkit
  • Not unlike jq (for JSON), Miller is written in portable, modern C, with zero runtime dependencies. You can download or compile a single binary, scp it to a faraway machine, and expect it to work.

Copyright (c) 2015- John Kerl

All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this
  list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice,
  this list of conditions and the following disclaimer in the documentation
  and/or other materials provided with the distribution.

This software is provided by the copyright holders and contributors "as is" and
any express or implied warranties, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose are
disclaimed. In no event shall the copyright holder or contributors be liable
for any direct, indirect, incidental, special, exemplary, or consequential
damages (including, but not limited to, procurement of substitute goods or
services; loss of use, data, or profits; or business interruption) however
caused and on any theory of liability, whether in contract, strict liability,
or tort (including negligence or otherwise) arising in any way out of the use
of this software, even if advised of the possibility of such damage.

I am providing code in this repository to you under an open-source license.
Because this is my personal repository, the license you receive to my code is
from me and not from my employer (Facebook).

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to


   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: 6F8C3F6F579712378E3D2E6C4FC175F4C2E39489CB75ECE0D75AB89B1285B187
   checksum64: 32A7407CE3302C9A4FDE00ECB6137C7B2B23CAACFF28B2CD3AF7096494286B1B

File 'license.txt' is obtained from:
md5: B5422B6A742EB6E7F3A5E16F308EA433 | sha1: C2110939439EBCB290E8F7714383F1640BEEFF78 | sha256: 6F8C3F6F579712378E3D2E6C4FC175F4C2E39489CB75ECE0D75AB89B1285B187 | sha512: 30777E2DEA4247819B929C8FE4DE34059A2E789FC505B36120F1960B9BB2B00ACA944E8B4BA8B7B97630DE0D60B53F7B66ADE078ACAEC3543D8941E81F4F5951
md5: 1764C2D0526F8ABE1D8199FF23208E3A | sha1: A77C0A894CB19D0A8CE49F79CE81DA61DED2E573 | sha256: 32A7407CE3302C9A4FDE00ECB6137C7B2B23CAACFF28B2CD3AF7096494286B1B | sha512: 2AEAF45E8E4F83011E40E14DBAFAE9639013CE58962B3206A24D456371844EF31710A9E67EE075FF17F7D9C7CD183A077D91958CE5F3050A8914C2CB65F9FF0D

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Miller 5.9.1 90 Friday, September 4, 2020 Approved
Miller 5.9.0 46 Thursday, August 20, 2020 Approved
Miller 5.7.0 54 Friday, June 5, 2020 Approved

This package has no dependencies.

Discussion for the Miller Package

Ground Rules:

  • This discussion is only about Miller and the Miller package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Miller, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus