Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support multitenancy

See original GitHub issue

Support multitenancy

I work on Spring-boot+Postgre application which works in multitenant-mode. Namely, we implemented AbstractRoutingDataSource and our solution is based on using ThreadLocal:

public class MyRoutingSource extends AbstractRoutingDataSource {
    @Override
    protected Object determineCurrentLookupKey() {
        return getNameOfTenantFromThreadLocal();
    }
    // ....
}

Ultimately I would like Shedlock to support the following:

single LockProvider bean (as it is now)
database for each tenant having own shedlock table
cache LockRecordRegistry be tenant-dependant (i.e. private final Set<String> lockRecords transform to private final Map<Object, Set<String>> lockRecords where Object is tenant identifier (same as in AbstractRoutingDataSource).

When I tried to supply instance of AbstractRoutingDataSource to JdbcTemplateLockProvider(myRoutingSource) then I’ve got runtime exception because initialization of new Bean isn’t bound to any tenant-context and SqlStatementsSource#getDatabaseProductName is trying to query DB during initialization.

Suggested improvement

Give option to configuration to rather directly specify database-used OR lazy initialize DB provider name. Example:

private static String getDatabaseProductName(Configuration configuration) {
        if (configuration.getPredifnedDatabaseProductName() != null) {
                return configuration.getPredifnedDatabaseProductName();
        }
        return configuration.getJdbcTemplate().execute((ConnectionCallback<String>) connection -> connection.getMetaData().getDatabaseProductName());
    }