David Scharf
David Scharf
Todo: * Do fixture with one claim * Think wether we should disable reclaiming until certain stages pass * Think about final / closed state * Think about support for...
### Description We want to add some rules how to name stuff (mostly branches). Let's discuss :)
GCS has an s3 interoperability mode which emulates s3. This way users could use the s3 bucket filesystem implementation with gcs. This is useful when loading to a final destination...
### Documentation description When doing any lookups by column value (mostly for merge writes) we should make the user aware of the fact that indexing is essential for some destinations...
Our pipeline object exposes a `sql_client()` method that can be used to directly access the current main destination storage if the destination is one of the sql destinations. It would...
### Feature description For properly releasing the generic destination we need to do the following: - [x] allow to set max_table_nesting in the decorator and pass it to normalizer via...
### Feature description We want to support synching state and schema info to a destination separate from the destinations the load data is sent to. This will be specially useful...
We want to enable the user to make use of AWS Athena partitions. For this we will most likely need to change the schema a bit and add the option...
The hints in extract info used to have a write_disposition, this is no longer present there. I'm not sure wether this is a bug or not, but it broke the...