Closed daniel-sudz closed 2 years ago
I found com.twitter.scalding.db
and looks like in the past there were plans to move jbdc in there but there was never any incentive to do so after a while.
based on https://github.com/twitter/scalding/pull/1382 twitter used/uses an internal implementation of jbdc for scalding
I don't remember, if jdbc was used at Twitter. scalding-db
for sure was. If @germanschnyder or @nownikhil could chime in.
we can revert this if Twitter corrects us later. Let's keep scalding-db for now.
Sorry for the delay, was out for few days. Verified that its not being used at Twitter. Thanks @daniel-sudz
based on https://github.com/twitter/scalding/issues/1968. We are not aware of any popular use of this module. Even if someone is using it it will likely need to be re-written in future scalding releases because:
I would prefer to reduce support burden on things that do not provide value to most consumers. This is also something that can implemented on the consumer side if it is really required.