Selection for partitioned in an AssetGroup

Summary

Hi everyone, I want to define multiple asset branches in a single AssetGroup and I would like each branch to be partitioned with a different start_date. So, I created several jobs using a selection. But obviously the asset selection for partitioning is done on the AssetGroup and not on the selection. What generates this exception : When an assets job contains multiple partitions assets, they must have the same partitions definitions, but asset '["branch_1_upstream"]' and asset '["branch_2_upstream"]' have different partitions definitions. Is there a solution to solve this problem? Thank you in advance

Reproduction

def make_asset_group(branch, date):
    daily = DailyPartitionsDefinition(start_date=date)
    
    @asset(
        name = f'{branch}_upstream',
        partitions_def=daily
    )
    def asset_upstream():
        ...

    @asset(
        name = f'{branch}_downstream',
        ins={"upstream": AssetIn(asset_key=AssetKey(f'{branch}_upstream'),
        partitions_def=daily
    )
    def asset_downstream(upstream):
        ...

    return [asset_downstream, asset_upstream]


assets_branch = make_asset_group(branch, date) for branch, date in {branch_1 : date_1, branch_2 : date_2}.items()

asset_group = AssetGroup(
  assets=[asset for assets in assets_branch for asset in assets]
)

job_1 = asset_group.build_job(
    selection = [branch_1_upstream, branch_1_downstream]
)
job_2 = asset_group.build_job(
    selection = [branch_2_upstream, branch_2_downstream]
)


@repository
def repository():
    return [asset_group, job1, job2]

Dagit UI/UX Issue Screenshots

Additional Info about Your Environment

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We factor engagement into prioritization.

[sryza]

@jburnich - yesterday’s release included a change that enables having assets with different partitions definitions within the same group. That turned out to make more sense than enabling multiple AssetGroups within the same repository.

I believe that should address the issue you raised here, so I’m going to close this. Feel free to reopen if not.

[jburnich]

Thanks for your quick return. Yes, that’s a good idea. I believe that if a repository can contain multiple AssetGroup where each AssetGroup has its own partitioning and scheduler, this would probably solve our problem. We look forward to testing this new feature.