data-versioning

alter table player_season_stat_totals add column league_id INT;
alter table player_season_stat_totals drop primary key;
alter table player_season_stat_totals add primary key (player_id, team_id, season_id, season_type_id, league_id);
update player_season_stat_totals set league_id=0;

get error: column <league_id> received nil but is non-nullable

Shouldn't be able to add primary

Description

We need to update our list of community developed plugins, as our ecosystem grows, this task focuses on adding the kedro-airflow-k8s plugin to our Community Developed Plugins page.

Possible Implementation

Follow the process in our [Contribution G

What

being able to take a data object (or prefix, like a partition) and get back the commit that added/modified it.

Why

This is valuable lineage information that is currently available in lakeFS but not exposed easily, and mimics the behavior of git blame

How

Given the lakeFS API already supports listing the log of commits for an object or prefix (🎉), this could be a `

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