influxdb/iox_catalog
Michael Gattozzi ff567cd33f
chore(deps): Update arrow and datafusion to 49.0.0 (#24605)
* chore(deps): Update arrow and datafusion to 49.0.0

This commit copies in our dependency code from influxdb_iox in order for
us to be able to upgrade from a forked version of 46.0.0 to 49.0.0 of
both arrow and datafusion. Most of the important changes were around how
we consumed the crates in influxdb3(_server/_write). Those diffs are
particularly worth looking at as the rest was a straight copy and we
don't touch those crates in our development currently for influxdb3
edge.

* fix: regenerate workspace hack crate

* fix: Protobuf issues with incompatibility labels

* fix: Broken CI yaml

* fix: buf version

* fix: Only check IOx repo

* fix: Remove protobuf lint

* fix: Comment out call to protobuf-lint
2024-01-31 19:18:51 -05:00
..
migrations chore(deps): Update arrow and datafusion to 49.0.0 (#24605) 2024-01-31 19:18:51 -05:00
sqlite/migrations chore(deps): Update arrow and datafusion to 49.0.0 (#24605) 2024-01-31 19:18:51 -05:00
src chore(deps): Update arrow and datafusion to 49.0.0 (#24605) 2024-01-31 19:18:51 -05:00
.gitignore feat: Initial SQLite catalog schema (#6851) 2023-02-06 22:55:14 +00:00
Cargo.toml chore(deps): Update arrow and datafusion to 49.0.0 (#24605) 2024-01-31 19:18:51 -05:00
README.md feat: retry failed migrations (#8414) 2023-08-04 11:15:05 +00:00
build.rs feat: allow IOx catalog to setup itself (no SQLx CLI required) (#3584) 2022-01-31 15:07:38 +00:00
check_linear_migrations.sh fix: make concurrent index creations idempotent (#8450) 2023-08-09 19:16:35 +00:00

README.md

IOx Catalog

This crate contains the code for the IOx Catalog. This includes the definitions of namespaces, their tables, the columns of those tables and their types, what Parquet files are in object storage and delete tombstones. There's also some configuration information that the overall distributed system uses for operation.

To run this crate's tests you'll need Postgres installed and running locally. You'll also need to set the INFLUXDB_IOX_CATALOG_DSN environment variable so that sqlx will be able to connect to your local DB. For example with user and password filled in:

INFLUXDB_IOX_CATALOG_DSN=postgres://<postgres user>:<postgres password>@localhost/iox_shared

You can omit the host part if your postgres is running on the default unix domain socket (useful on macos because, by default, the config installed by brew install postgres doesn't listen to a TCP port):

INFLUXDB_IOX_CATALOG_DSN=postgres:///iox_shared

You'll then need to create the database. You can do this via the sqlx command line.

cargo install sqlx-cli
DATABASE_URL=<dsn> sqlx database create
cargo run -q -- catalog setup

This will set up the database based on the files in ./migrations in this crate. SQLx also creates a table to keep track of which migrations have been run.

NOTE: do not use sqlx database setup, because that will create the migration table in the wrong schema (namespace). Our catalog setup code will do that part by using the same sqlx migration module but with the right namespace setup.

Migrations

If you need to create and run migrations to add, remove, or change the schema, you'll need the sqlx-cli tool. Install with cargo install sqlx-cli if you haven't already, then run sqlx migrate --help to see the commands relevant to migrations.

Tests

To run the Postgres integration tests, ensure the above setup is complete first.

CAUTION: existing data in the database is dropped when tests are run, so you should use a DIFFERENT database name for your test database than your INFLUXDB_IOX_CATALOG_DSN database.

  • Set TEST_INFLUXDB_IOX_CATALOG_DSN=<testdsn> env as above with the INFLUXDB_IOX_CATALOG_DSN env var. The integration tests will pick up this value if set in your .env file.
  • Set TEST_INTEGRATION=1
  • Run cargo test -p iox_catalog

Schema namespace

All iox catalog tables are created in a iox_catalog schema. Remember to set the schema search path when accessing the database with psql.

There are several ways to set the default search path, depending if you want to do it for your session, for the database or for the user.

Setting a default search path for the database or user may interfere with tests (e.g. it may make some test pass when they should fail). The safest option is set the search path on a per session basis. As always, there are a few ways to do that:

  1. you can type set search_path to public,iox_catalog; inside psql.
  2. you can add (1) to your ~/.psqlrc
  3. or you can just pass it as a CLI argument with:
psql 'dbname=iox_shared options=-csearch_path=public,iox_catalog'