_get_infer_single_to_multi_dimension_deps_result is to restrictive, can't handle identityMapped staticPartitionDefintions

[ion-elgreco]

Dagster version

1.7.5

What's the issue?

I have two upstream assets, with these partition defintions:

Asset_1:

partitions_def=MultiPartitionsDefinition(
        {
            "month": MonthlyPartitionsDefinition(start_date="202105", fmt="%Y%m", end_offset=1),
            "code": StaticPartitionsDefinition(["FOO"]),
        },
    ),

Asset_2:

    partitions_def=MultiPartitionsDefinition(
        {
            "month": MonthlyPartitionsDefinition(start_date="202105", fmt="%Y%m", end_offset=1),
            "code": StaticPartitionsDefinition(["FOO", "BAR"]),
        },
    ),

Asset 1 and Asset 2 are inputs for Asset 3, where Asset 3 has this single partitionDefinition: StaticPartitionsDefinition(["FOO"])

In my AssetIn I declare each asset_1 and asset_2 to have this mapping: MultiToSingleDimensionPartitionMapping("code"), which results in this error, and that's only because Dagster checks whether the definitions completely match. But with StaticPartitionDefintions it should be possible to also have a subset or no match at all.

dagster._check.CheckError: Failure condition: MultiToSingleDimensionPartitionMapping can only be used when: 
(a) The single dimensional partitions definition is a dimension of the MultiPartitionsDefinition.
(b) The single dimensional partitions definition is a TimeWindowPartitionsDefinition and the MultiPartitionsDefinition has a single time dimension.

If I don't provide a mapping at all, I get even a stranger error:

dagster._core.errors.DagsterInvariantViolationError: Partition key range PartitionKeyRange(start='FOO', end='FOO') in asset_3 depends on invalid partition keys ['FOO'] in upstream asset AssetKey(['feat-partitioning-assets', 'asset_2'])

What did you expect to happen?

Make the multiToSinglePartitionMapping usable

How to reproduce?

No response

Deployment type

None

Deployment details

No response

Additional information

No response

Message from the maintainers

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