How good is the support for creating partitioned assets that are not time-based? It seems most of the documented examples are for things like hourly, weekly, daily etc. If I wanted to create a partition that is based on something that is not time based, should I be worried about running into issues because partitions are assumed to be time-based? For some context, I would like to use something akin to customerID, where we are wanting to materialize specific assets for each customer. I don't want to use a static partition -- because we expect to add customers.

Dagster definitely supports non-time partitioned assets / jobs. See static partitions and dynamic partitions. Though I would agree that the vast majority of docs seem to be geared toward time-based partitions and it'd be nice to see more examples, particularly for dynamic partitions. I'm currently using static partitions in a basic job to track a similar concept (credential_id for credentials that need to be rotated) I think there's just a lot more functionality implemented around time-based partitions because the problem and desired feature-set is more well-defined.

Agree that we could do a much better job of improving example documentation about the use cases for different partitions definitions. I think dynamic partitions are a good use case for you since you expect to add customers. We'll release documentation for this later today, but here's a link to the unreleased examples: https://docs.dagster.io/master/concepts/partitions-schedules-sensors/partitions#dynamically-partitioned-assets

Glad to see this on the roadmap! I think this will be a really killer feature. I will likely hold off on this for now and just rely on sensors/jobs to trigger a new run as needed.

@Ryan Ernst - to be clear, dynamic partitions are already in the latest release of Dagster (still marked experimental), so you can try them out whenever you're ready