Skip to main content

FXMacroData for Apache NiFi

FetchFXMacroData is an Apache NiFi 2 Python processor that fetches one FXMacroData operation per trigger and emits a FlowFile with the complete response. Route macro announcements, release calendars, FX, commodities and positioning data into any NiFi flow without writing an HTTP client.

FXMacroData documentation

Install

Requires Apache NiFi 2.0 or later with Python processors enabled (nifi.python.command in nifi.properties) and Python 3.10 or later on the NiFi host. Copy src/fxmacrodata_nifi/FetchFXMacroData.py into NiFi's Python extensions directory (python_extensions/ by default). The processor declares fxmacrodata-platform-core==0.1.0 as its dependency; make that package and its adjacent fxmacrodata-public-client available to NiFi's Python environment from the distribution supplied to you, for example by pointing NiFi's pip index at a local directory that contains both, or by installing them into the interpreter NiFi uses:

python -m pip install /path/to/fxmacrodata-public-client /path/to/fxmacrodata-platform-core

NiFi supplies the nifiapi module at run time. The package carries a small _shim module with the same names so the processor can be imported and tested outside NiFi; it is never used inside NiFi.

Configure

Add FetchFXMacroData to the canvas and set its properties:

Property Description
Operation One of the 87 documented operations; MCP tools carry an mcp_ prefix.
Arguments JSON object of operation arguments, for example {"currency": "usd", "indicator": "policy_rate"}.
API Key Env Name of the environment variable holding your API key (for example FXMD_API_KEY). Leave empty for anonymous access.
Complete History true follows every page of a historical operation; false fetches the supplied page only.
Max Pages Upper bound on pages followed for a complete history (default 10000).

USD data works without a key: Operation indicator_history, Arguments {"currency": "usd", "indicator": "policy_rate"}. Schedule the processor with a timer or cron run schedule.

Credentials

Set the API key in the environment of the NiFi process (or its Python sub-process) and give the processor only the variable's name. The processor resolves the value at run time, never stores it in the flow definition and never writes it to attributes, content or logs. Arguments carrying api_key, tokens, URLs or endpoint overrides are rejected before any request.

FlowFile output

Each successful trigger routes one FlowFile to success with content

{"operation": "indicator_history", "source_url": "<publisher URL>", "rows": [...]}

and attributes mime.type, fxmacrodata.operation, fxmacrodata.source_url, fxmacrodata.row_count and fxmacrodata.complete_history. Each row carries operation, source_url, record_id, currency, indicator, date, announcement_datetime, value, value_text, record_json and response_json. Only value is numeric (nullable); every other field is a nullable string. record_json retains the original record and response_json the complete response, including pagination and revision metadata. An empty response produces one row with record_json of null; it is not an observation. Dates and announcement times remain source strings, no publication time is inferred and no missing value is filled. record_id is a stable hash of the operation and record, so repeated fetches of unchanged data produce the same identifiers.

Invalid configuration or a failed read routes one FlowFile to failure with a fxmacrodata.error attribute and a JSON {"error": ...} body. The message never contains credentials or upstream diagnostics.

Delivery guarantee

Each trigger performs one fresh read; the processor keeps no state. Delivery into your flow is at-least-once per schedule. Deduplicate downstream on operation and record_id (for example with DetectDuplicate or a MERGE in your sink) when a sink requires exactly-once storage.

Development

Run the offline tests with python -m pytest tests -q. They instantiate the processor with the shim, fake the NiFi context and monkeypatch the public reader; they never call the live service.

Metadata

Release files for nifi-fxmacrodata 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nifi-fxmacrodata 0.1.0
File Size Uploaded Provenance Actions
nifi_fxmacrodata-0.1.0.tar.gz 9.2 kB Without provenance Details for nifi_fxmacrodata-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for nifi-fxmacrodata 0.1.0
File Interpreter ABI Platform Actions
nifi_fxmacrodata-0.1.0-py3-none-any.whl Python 3 none any Details for nifi_fxmacrodata-0.1.0-py3-none-any.whl

Total release size: 17.4 kB

Release files / nifi_fxmacrodata-0.1.0.tar.gz

Download URL nifi_fxmacrodata-0.1.0.tar.gz
Size 9.2 kB
Tags Source
SHA-256 checksum
How to use checksums
78ac6206ad21b0b58ec1a3a0dbde170f8d65370e3e3650feffe9748ad6f0d498
BLAKE2b-256 checksum
How to use checksums
c2290cee784ed212821162637388dec2d6be7f851b59f56cc128ce2006f91d35
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via FXMacroData-PackagePublisher/1.0

Release files / nifi_fxmacrodata-0.1.0-py3-none-any.whl

Download URL nifi_fxmacrodata-0.1.0-py3-none-any.whl
Size 8.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ee9ad677e2a361fb648acf3ec5b6b5c3fbef547981789b2eef4e8922b6380f85
BLAKE2b-256 checksum
How to use checksums
0631ac1bfd9874335b89d30b3c8d8f1615771e4422f97314a63949265f08c348
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via FXMacroData-PackagePublisher/1.0

Security for nifi-fxmacrodata 0.1.0

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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page