I think that since it's 2.0 and we'll be offering multiple-backends that the original constructor doesn't make much sense. The TSDB should build the proper storage client and hand it off to anything that needs to use it. The getClient() call is just a stop gap too.