Yeah, I had the same thought. Talked to @jcarouth about it a few nights ago and it seems as though there really isn't going to be any reason to need to override it. For example, if we did change the name of the table and overrode it, we'd have to go in and either A) change the value of the default or B) update all the instances of the TagService to override the default.

Since A seems like it'd be the most sane way to update it, I'd argue that the configuration isn't even really serving it's own purpose. If we hard coded the table name into the query and it had to change, we'd just change it and not have to worry about all the times its instantiated, or instances where it was mistakenly overridden or explicitly populated with the same value as the default. You'd like to think we'd catch that up front, but you never know.