Export CSV To Influx
Export CSV To Influx: Process CSV data, and export the data to influx db
Install
Use the pip to install the library. Then the binary export_csv_to_influx is ready.
` pip install ExportCsvToInflux `
Features
Allow to use binary export_csv_to_influx to run exporter
Allow to check dozens of csv files in a folder
Auto convert csv data to int/float/string in Influx
Allow to limit string length in Influx
Allow to judge the csv has new data or not
Allow to use the latest file modify time as time column
Auto Create database if not exist
Allow to drop database before inserting data
Allow to drop measurements before inserting data
Allow to match or filter the data by using string or regex.
Allow to count, and generate count measurement
Command Arguments
You could use export_csv_to_influx -h to see the help guide.
-c, –csv, Input CSV file path, or the folder path. -d, –delimiter, CSV delimiter. Default: ‘,’. -lt, –lineterminator, CSV lineterminator. Default: ‘n’. -s, –server, InfluxDB Server address. Default: localhost:8086 -u, –user, InfluxDB User name. -p, –password, InfluxDB Password. -db, –dbname, InfluxDB Database name. -m, –measurement, Metric column name. -t, –time_column, Timestamp column name. Default: timestamp. If no timestamp column, the timestamp is set to the last file modify time for whole csv rows. -tf, –time_format, Timestamp format. Default: ‘%Y-%m-%d %H:%M:%S’ e.g.: 1970-01-01 00:00:00. -tz, –time_zone, Timezone of supplied data. Default: UTC. -fc, –field_columns, List of csv columns to use as fields, separated by comma. Mandatory -tc, –tag_columns, List of csv columns to use as tags, separated by comma. Mandatory -b, –batch_size, Batch size when inserting data to influx. Default: 500. -lslc, –limit_string_length_columns, Limit string length column. Default: None. -ls, –limit_length, Limit length. Default: 20. -dd, –drop_database, Drop database before inserting data. -dm, –drop_measurement, Drop measurement before inserting data. -mc, –match_columns, Match the data you want to get for certain columns, separated by comma. -mbs, –match_by_string, Match by string, separated by comma. -mbr, –match_by_regex, Match by regex, separated by comma. -fic, –filter_columns, Filter the data you want to filter for certain columns, separated by comma. -fibs, –filter_by_string, Filter by string, separated by comma. -fibr, –filter_by_regex, Filter by regex, separated by comma. -ecm, –enable_count_measurement, Enable count measurement. -fi, –force_insert_even_csv_no_update, Force insert data to influx, even csv no update.
For more info, please refer to the https://github.com/Bugazelle/export-csv-to-inlfux
Metadata
Release files for ExportCsvToInflux 0.1.4
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 |
|---|---|---|---|---|
| ExportCsvToInflux-0.1.4.tar.gz | 9.5 kB | Without provenance | Details for ExportCsvToInflux-0.1.4.tar.gz |
Release files / ExportCsvToInflux-0.1.4.tar.gz
| Download URL | ExportCsvToInflux-0.1.4.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6458396ae7c9b416f60806d3b56ca8d995c40dc013fda8d7542da547551d5cb3
|
|
BLAKE2b-256 checksum How to use checksums |
5889932dce79fcaa51bfd60810a20491dadd51d26dcd23dd743c32fdef3aae6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.19.1 setuptools/18.5 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.10
|
Security for ExportCsvToInflux 0.1.4
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.