We’ve had a lot of success using the ARP JDBC plugin framework.
We’d like to be able to make pre/post SQL calls whenever a connection is retrieved/returned to the connection pool; if we had to override JdbcConf.newPlugin and provide an extended version of JdbcStoragePlugin that would be fine. We’d also like to have access to the querying user at this scope, so we could set session parameters on the database. These querying user details are outside the scope of dataset security, that we could achieve with checkAccess.
In practice I think this would mean JdbcRecordReader would need the username, and during setup it could pass us a copy along with the connection object already pulled from the pool, and again on cancel/close for cleanup.
Thanks for the comment and request. Adding the ability to specify SQL to run before/after queries is something we have looked at but do not have a timeframe on at this time. Out of curiosity, would the pre SQL calls that set session parameters based on the username change the structure of tables returned in your case? For example would different users see different columns masked at the source level after the per user session parameters were set? Thanks, Tom
It does not change the schema of the result set. We use it to execute internal row level security.
I would be happy to make the change myself, and even run a customized version, except it’s my understanding that the license associated with this library does not allow me to do that.
It would be great to see this wrapper library also put up on the Hub and have it’s licensed changed to Apache
