chain
, transaction_hash
, and log_index
as the primary key.
Because The Indexing Company’s pipelines guarantee at-least-once delivery, duplicates can occur during retries. The unique key constraint ensures that only one version of each event is stored reliably.
Make sure the schema matches the structure and types you expect to receive at scale. Once ready, you’re good to move on to deployment.
💡 You can use tools like ChatGPT or jsonschema2ddl
to help generate your table schema from a JSON example like the one above. Here’s a quick tutorial including the prompts.
6. Deploy Pipeline
With the transformation logic, contract filter, and destination schema ready, you can now deploy the full pipeline. This step registers all components together so The Indexing Company can begin streaming data from the blockchain to your destination.
You’ll need to provide:
aave_example
if following Part 1)aave_example_filter
) and filterKeys. The FilterKey is the parameter to filter on. In our case the contract_address
networks
in this case ethereum
, but feel free to add other chains if the event signatures and contracts filters apply on those too, like base
postgres
, webhook
, etc.)curl
to deploy a pipeline to PostgreSQL:
https://app.indexing.co/dw/pipelines/