guillesd

Related to this issue --> https://github.com/sodadata/soda-sql/issues/676

I think this is a bit related to my issue https://github.com/databrickslabs/dbx/issues/713, dbx creates a directory everytime you do a deployment but I wonder how it can keep track of all...

I think the problem may be in `mlflow.log_artifact()` function which is used by [MlflowFileUploader](https://github.com/databrickslabs/dbx/blob/4c221a95c0cca148f5e6f2ae1ce1be5dcaaebd49/dbx/utils/file_uploader.py#L64), which is instantiated in the `deploy()` command: https://github.com/databrickslabs/dbx/blob/dc0dd54be26de53b27c054400ec8c3c442bc8c2c/dbx/commands/deploy.py#L139

Hi @renardeinside, Could you explain why this is required for proper versioning? Versioning for us happens in our Git provider, for us `dbx deploy` is a way to sync our...

@renardeinside would you consider a PR for this?

I 100% agree with @allebacco, we need a new implementation of the AbstractFileUploader that offers an alternative to the default MLFlow uploader, and that potentially exposes more control over where...

The key seems to be here: https://github.com/sodadata/soda-sql/blob/dc31150e3de38060683d27ed1e5bff5b6ec2802e/core/sodasql/scan/parser.py#L174 I think `env_required` should be set to `true`

FYI https://ducklake.select/docs/preview/duckdb/guides/access_control. Going deeper than this is out of the scope of an Open Table format (or Lakehouse format). This functionality usually resides in an external service (for example Unity...

@biellls I think DuckLake has many selling points, some that come to mind: - Simplicity: metadata stored in a db with a simple star schema - Speed: avoid unnecessary metadata...

Hi there! Yes we are looking into this! Sorry for the delay!