> Productive no-sql data sources exploration with SQL, Pandas and
> shortcuts
| service | status |
| --------------------- |:-------------:|
| travis | [](https://travis-ci.org/hackliff/mgocli) |
| quay.io/hackliff/drill | [](https://quay.io/repository/hackliff/drill) |
## Getting started
`make container.build` will start and initialize [MongoDB](), [Drill]()
and `datacli` with everything installed.
It is still possible to register external data sources :
```Bash
$ cp ./tools/drill/mongo-storage-plugin.json custom-storage.json
$ $EDITOR custom-storage.json
$ ./tools/drill/manage.sh storage ./custom-storage.json http://$(docker-machine ip default):8047
{
"result" : "success"
}
```
## Usage
### Mgocli
```Bash
$ ./datacli/__main__.py -H $(docker-machine ip default) appturbo
[2016-07-06 06:38:24,564] datacli :: INFO - connected to Drillbit
[ datacli::192.168.99.100::appturbo ] >>> SHOW DATABASES
[2016-07-06 06:38:48,391] datacli :: INFO - sending query to drill
[show databases]
SCHEMA_NAME
0 INFORMATION_SCHEMA
1 cp.default
2 dfs.default
3 dfs.root
4 dfs.tmp
```
### Drill Repl
```sql
$ # query data
$ docker exec -it $(basename $PWD)_drill_1 /opt/apache-drill-1.7.0/bin/drill-localhost
0: jdbc:drill:drillbit=localhost> SHOW DATABASES;
+---------------------+
| SCHEMA_NAME |
+---------------------+
| INFORMATION_SCHEMA |
| cp.default |
| dfs.default |
| dfs.root |
| dfs.tmp |
| nosqltest.employee |
| nosqltest.local |
| nosqltest.test |
| sys |
+---------------------+
9 rows selected (0.244 seconds)
0: jdbc:drill:drillbit=localhost> SELECT * FROM nosqltest.test.zips
LIMIT 3;
+--------+----------+-------------------------+--------+--------+
| _id | city | loc | pop | state |
+--------+----------+-------------------------+--------+--------+
| 01001 | AGAWAM | [-72.622739,42.070206] | 15338 | MA |
| 01002 | CUSHMAN | [-72.51565,42.377017] | 36963 | MA |
| 01005 | BARRE | [-72.108354,42.409698] | 4546 | MA |
+--------+----------+-------------------------+--------+--------+
3 rows selected (0.325 seconds)
0: jdbc:drill:drillbit=localhost> !quit
```
1 maintainer
Metadata
1 maintainer
Release files for datacli 0.1.3
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 |
|---|---|---|---|---|
| datacli-0.1.3.tar.gz | 4.4 kB | Without provenance | Details for datacli-0.1.3.tar.gz |
Release files / datacli-0.1.3.tar.gz
| Download URL | datacli-0.1.3.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7fd2bca73df8c325b149a9af67962caf6e2276236100cf9d716478dc5837e31
|
|
BLAKE2b-256 checksum How to use checksums |
a32cf9ab4842b18954fa9702e5612d13d9b2e98892269213aeb961c23e25ee7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for datacli 0.1.3
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.
