servify
Biblioteca Python para leitura de dados (xlsx/csv/json/parquet/delta/tabelas) em ambientes Databricks, com detecção automática de encoding/delimitador/JSON multiline e logging integrado.
Instalação
pip install servify
Uso rápido
import servify as sf
df = sf.read_data(
"/Volumes/meu_catalogo/meu_schema/volume/arquivo.csv", "csv")
Configuração (opcional)
Antes de chamar sf.read_data(...), o usuário pode ajustar as opções abaixo
diretamente em sf.<opção> = valor:
import servify as sf
sf.show_options() # lista todas as opções disponíveis e o valor atual de cada uma
sf.LOG_ENABLED = True # exibe logs no terminal (default: False)
sf.PERSIST_LOGS_CATALOG = "meu_catalogo" # catalog do Unity Catalog p/ persistir logs
sf.PERSIST_LOGS_SCHEMA = "meu_schema" # schema do Unity Catalog p/ persistir logs
sf.PERSIST_LOGS = True # persiste logs em tabela Delta (default: False)
sf.PERSIST_LOG_MIN_LEVEL = "ERROR" # nível mínimo persistido (default: "WARNING")
df = sf.read_data(
"/Volumes/meu_catalogo/meu_schema/volume/arquivo.csv", "csv")
| Opção | Tipo | Default | Observação |
|---|---|---|---|
LOG_ENABLED |
bool | False |
Exibe logs no terminal. |
PERSIST_LOGS |
bool | False |
Persiste logs em tabela Delta do Unity Catalog. |
PERSIST_LOGS_CATALOG |
str | None |
Necessário antes de PERSIST_LOGS = True. |
PERSIST_LOGS_SCHEMA |
str | None |
Necessário antes de PERSIST_LOGS = True. |
PERSIST_LOG_MIN_LEVEL |
str | "WARNING" |
DEBUG, INFO, WARNING, ERROR ou CRITICAL. |
O que acontece se catalog / schema não forem informados?
Se sf.PERSIST_LOGS = True for definido sem PERSIST_LOGS_CATALOG e
PERSIST_LOGS_SCHEMA já preenchidos, a lib não levanta exceção: ela imprime
um aviso ([WARN] persist_logs não habilitado: ...) e mantém PERSIST_LOGS
como False até que ambos sejam definidos. Ou seja, o comportamento padrão
(sem persistência) continua funcionando normalmente; a persistência em Delta é
sempre opt-in e só é ativada quando catalog e schema estão presentes.
import servify as sf
sf.PERSIST_LOGS = True
# [WARN] persist_logs não habilitado: informe 'catalog' e 'schema' do Unity
# Catalog (ex.: sf.PERSIST_LOGS_CATALOG e sf.PERSIST_LOGS_SCHEMA) antes de
# sf.PERSIST_LOGS = True.
sf.PERSIST_LOGS_CATALOG = "meu_catalogo"
sf.PERSIST_LOGS_SCHEMA = "meu_schema"
sf.PERSIST_LOGS = True # agora habilita normalmente
Licença
MIT
Metadata
Release files for servify 0.1.6
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 |
|---|---|---|---|---|
| servify-0.1.6.tar.gz | 23.4 kB | Without provenance | Details for servify-0.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| servify-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for servify-0.1.6-py3-none-any.whl |
Total release size: 56.4 kB
Release files / servify-0.1.6.tar.gz
| Download URL | servify-0.1.6.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b0ab8c7a065f55ce55046871bddc7582be6d93da9a0a7dc5906665665c6a5a1
|
|
BLAKE2b-256 checksum How to use checksums |
b36a53171d6180ba8361ed214a5b8608adfdc129b5eea880eaba5a34815b354b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / servify-0.1.6-py3-none-any.whl
| Download URL | servify-0.1.6-py3-none-any.whl |
|---|---|
| Size | 33.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed7fbe1f75638e2eb82d93c562107f118093a6daa0115364bdbe4f0585308abb
|
|
BLAKE2b-256 checksum How to use checksums |
ba35760e5c280b6117ecef34ea5d6e66dda13f9512c531c8487df006b2012270
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for servify 0.1.6
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.