How to have a job materializing two assets with different partition definitions?

[DourivalPimentel]

Let's assume I have defined two assets which I want to parallelize to increase performance and they depend on each other:

@asset(
    partitions_def=StaticPartitionsDefinition(["1", "2", "3"])
)
def first_asset(context: AssetExecutionContext):
    ...

@asset(
    partitions_def=StaticPartitionsDefinition(["1", "2", "3", "4", "5"]),
    deps=[AssetDep(SourceAsset("first_asset"),  partition_mapping=AllPartitionMapping())],
)
def second_asset(context: AssetExecutionContext, first_asset: dict):
    ...

Since I am only partitioning for a performance increase, all the partitions on the second asset needs to wait for the partitions on the first asset to be completed and the partitioning on the second asset will be calculated through other means, not by direct mapping the partitions from the first one.

What is the best way to do that with Dagster Jobs?

[Micropot]

Hello there,
I have the same issue. Have you found any solution yet ?
I have partitions with diferents defintion start dates and i want a job/button to launch all the materialization of the assets