Hi everyone, I have a repository with 2 pipelines using the same solids and I’m getting the “Duplicate solids found in repository with name ‘name’. Solid definition names must be unique within a repository” message. The obvious fix would be to give each solid an alias with a prefix for corresponding pipeline or something like that but I’m wondering if there isn’t a better way to do this ? Maybe at the pipeline level, so all solids within the pipeline get a prefixed name or end up unique ? Thanks for your help !

so there is a difference between solid definitions and solid invocations invocations of the same solid will get aliased automatically we currently don’t allow duplicate definitions to allow for unique identifications of the solids that are invoked in potentially many places within a repository

Yes I’m currently calling the same solid in both pipelines so what you’re saying is if I were to remove the “name” argument it would work because each invocation would get aliased automatically otherwise I would have to use a

dagster.SolidDefinition

instead of a

@dagster.solid

? How would one do that ?

@solid

makes a

SolidDefinition

f I were to remove the “name” argument

what are you passing name to in this context?

@solid

? Might be useful to send a small code snippet

class SimpleProcessor(BaseProcessor, ABC):
    @classmethod
    def definition(cls, name: Optional[str] = None) -> SolidDefinition:
        return solid(
            name=name if name is not None else cls.info.name,
            description=cls.info.description,
            input_defs=cls._input_defs,
            output_defs=cls._output_defs,
            config_schema=cls._config_schema,
        )(cls._algorithm)

And then this is called this way in two different pipelines:

result = SimpleProcessor.definition(
        "signal_filter"
    )(signal=signal)

ya giving them different names will work and will be the easiest fix if everything is actually the same between these two SolidDefinitions - you just need to make this function return the same instance of the object ie memoizing manually or using something like

@lru_cache

.

Ah great ! thanks for the memoization tip 👍