Releases: streamingfast/substreams-sink-sql
Releases · streamingfast/substreams-sink-sql
v4.0.0-rc.3
- Fix a critical bug breaking the reorg management when more than one row needs to be reverted.
v4.0.0-rc.2
- Support more networks with default mappings (ex: solana, soon: optimism, soon: bitcoin)
- Add command "create-user " to help creating more SQL users, read-only or otherwise
- add 'enabled' field under "DBTConfig"
- Removed PgwebFrontend and WireProtocolAccess fields from the SinkConfig message: they will now be deployed when on a development environment, so they are not mentionned here anymore.
protodefs-v1.0.7
remove wire_protocol_access
from Service
protodefs-v1.0.6
remove pgweb from Service definition, add enabled field to DBTConfig
v4.0.0-rc.1
Fixes
- Fix an issue preventing the
setup
command from running on a clickhouse backend because of the reorg settings.
v4.0.0-beta
Highlights
- This release brings support for managing reorgs in Postgres database, enabled by default when
--undo-buffer-size
to 0.
Breaking changes
-
A change in your SQL schema may be required to keep existing substreams:SQL integrations working:
- The presence of a primary key (single key or composite) is now MANDATORY on every table.
- The
sf.substreams.sink.database.v1.TableChange
message, generated inside substreams, must now exactly match its primary key with the one in the SQL schema. - You will need to re-run
setup
on your existing PostgreSQL databases to add thesubstreams_history
table. You can use the new--system-tables-only
flag to perform only that.
-
Since reorgs management is not yet supported on Clickhouse, users will have to set
--undo-buffer-size
to a non-zero value (12
was the previous default)
protodefs-v1.0.5
Added run_interval_seconds
to DBTConfig to allow user to define how regularly the dbt run
command is executed.
protodefs-v1.0.4
Added support for rest_frontend
field in protobuf definition.
This is aimed at this backend implementation: https://github.com/semiotic-ai/sql-wrapper (only clickhouse is supported at the moment)
Example:
schema: "./schema.sql"
engine: clickhouse
rest_frontend
enabled: false
v3.0.5
- Fixed regression:
run
command was incorrectly only processing blocks staying behind the "FinalBlocks" cliff.
v3.0.4
- Fixed support for tables with primary keys misaligned with
database_changes
's keys (fixing Clickhouse use case)