This release is a pre-release and may not be stable for production use.
Metrique
Python/MongoDB Information Platform and Data Warehouse
Metrique help bring data into an intuitive, indexable data object collection that supports quick snapshotting, advanced ad-hoc querying, including (mongodb) aggregations and mapreduce, along with python, ipython, pandas, numpy, matplotlib, and so on, is fully integrated with the scientific python computing stack. I hope so anyway. :)
Author: “Chris Ward” <cward@redhat.com>
Sources: https://github.com/drpoovilleorg/metrique
Installation
You must first install MongoDB. Then, to continue, make sure it’s started.
Metrique (suggested) Install virtualenv and create a new virtual environment for metrique. Activate it.
Install metrique:
python-pip install metrique -r requirements.txt
You should now be ready to go.
Run metrique-server-config.py if you changed any defaults.
To start metrique, run:
$[/metrique/server/bin] metrique-server start [2|1|0] [1|0]
Where argv are debug on+/on/off and async on/off respectively.
It’s suggested to run :mod:metrique-server-setup after install as well, especially if you changed any default values of your mongo or metrique servers, they’re hosted on a different ip than localhost.
Client If the metrique server is running on anything other than http://127.0.0.1, run metrique-client-setup.
Then, launch a python shell. We suggest ipython notebook.
As of this time, :mod:cubes can be found in global metrique namespace or local to the running user.
Default: ~/.metrique/cubes
To quickly make those cubes available in sys.path:
IN [] from metrique.cubes import set_cube_path IN [] set_cube_path() # defaults to '~/.metrique/cubes'
Then, to load a cube for extraction, query or administration, import:
IN [] from git_repo.gitrepo import Commit IN [] g = Commit(config_file=None, uri=None)
Ping the server to ensure your connected. If all is well, metriqe server should pong your ping!:
IN [] g.ping() OUT [] pong!
Try running an example ::mod:git_commit etl job, for example:
IN [4] g.extract("git_commit")
Then, analyse away:
IN [5] q = c.query.fetch('git_commit', 'author, committer_ts')
IN [6] q.groupby(['author']).size().plot(kind='barh')
OUT [6] <matplotlib.axes.AxesSubplot at 0x6f77ad0>
Metadata
Release files for metriqued 0.1.3-alpha32
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| metriqued-0.1.3-alpha32.tar.gz | 42.2 kB | Without provenance | Details for metriqued-0.1.3-alpha32.tar.gz |
Release files / metriqued-0.1.3-alpha32.tar.gz
| Download URL | metriqued-0.1.3-alpha32.tar.gz |
|---|---|
| Size | 42.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4a03025de3304ffe6f4af728707502274e30dbad7f2fba2dfa64c0a8ea56cdd
|
|
BLAKE2b-256 checksum How to use checksums |
cfa5b34c3072e1f5d280995cc9d816503695b54d68d08247d98ff86a7b6a12be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for metriqued 0.1.3-alpha32
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.