data-version-control

Consider the following table:

dsimple> create table t(val char(3));
dsimple> insert into t values ('dasdsa');
string is too large for column

Dolt should add to the error message the name of the offending column like mysql

mysql> insert into t values ('dasdsa');
ERROR 1406 (22001): Data too long for column 'val' at row 1

We support toml as params file. There are a few issues with our current toml parsing:

1. We use toml library, which is not toml 1.0 standard compatible. Also, the library is not being actively maintained.
2. toml dumping does not preserve existing formatting.
3. iterative/dvc#6402

We can try migrating to tomli (which

🚨🚨 Feature Request

• A new implementation (Improvement, Extension)

Is your feature request related to a problem?

Currently, if a user tries to access an index that is larger than the dataset length or tensor length, an internal error is thrown which is not easy to understand.

Description of the possible solution

We can catch the error and throw a more descriptive e

On more advanced versions of LakeFS (probably > = v1.0.0), we would like to remove the logic that tries to fill the generation field in DB when loading old dumps. It means we will no longer support loading dump that made with a version lower than v0.61.0.

Currently the custom serializers are tested through the integration tests. Additional unit tests would be helpful for future backwards compatibility and finding issues faster.

While API action names have been renamed to refer to tag, there are some cases where parameter names and returned struct keys still refer to version.

Examples:

• in resource_show_tag: version_id parameter, version_metadata in the returned dict
• Same in package_show_tag