elt

Tell us about the problem you're trying to solve

When building a connector, one of the most important requirements is to define the output schema of each stream in the connector. There are multiple ways of doing this:

1. Transcribing the JSONSchema by hand based on reading API docs
2. Using the API's OpenAPI spec to discern the schema. [Docs](https://docs.airbyte.com/connector-development/c

Sending a rest call to delete a job specification throws 404 where as grpc call works fine. Steps to reproduce

curl -X DELETE "http://localhost:9100/v1/project/my-project/namespace/kush/helloworld" -H  "accept: application/json"

User story

As a user, I quickly want to connect my Snowflake data warehouse with Kuwala to start applying transformations. I only want to put in my credentials and establish the connection. Once connected, I want to see the database schema to see all available tables. For every existing table, I want to see a preview of the data and the column types.

Acceptance criteria

• The

I'm new to the idea of Data Vault 2.0 and I'm reading the Dan Linstedt book to understand it better.

To help me get a better perspective of how dbtvault works I would like to know how difficult do you think it would be to add support for BigQuery?

Are there specific features of Snowflake which makes it better for running dbt/dbtvault ?

Thanks,
Jacob

What is the feature request? What problem does it solve?
We need to integrate some static code analysis in order to be able to better ensure code quality and security.

Suggested solution
In the current Github Org SonarCloud and/or Codecov are approved so we should use one (or both) of them.

Additional context
This also was found as a gap in the evaluation https://bestpracti

Describe the bug
At the moment, Temporary tables names are created using:
https://github.com/astro-projects/astro/blob/9a565e8fa0fa68b4be0c0dbd1866e0b531b8b902/src/astro/sql/table.py#L78-L86

Where MAX_TABLE_NAME_SIZE is currently 63 characters (e.g. Postgres does not support tables with longer names).

The problem is that depending on the DAG ID and the task names, there will be colli

wikirepo as a project has many modules that interconnect and are funneled to two functions - wikirepo.data.query and lctn_utils.gen_lctns_dict. It would be helpful for users and potential contributors to have a visual representation of