Ashhar Hasan
Ashhar Hasan
cc: @djsstarburst
449 should have some improvements in this area - https://github.com/trinodb/trino/pull/22011, https://github.com/trinodb/trino/pull/22004 and https://github.com/trinodb/trino/pull/22003 should help a bit.
/test-with-secrets sha=9d7bd1dcad92de70856b928a99e443ec3d8b4619
see https://github.com/trinodb/trino/pull/21017#discussion_r1536270950, I think it's an important question.
@anoopj Do you plan to continue this? Or should someone else pick this up and drive to completion? I see that the newer client is released already.
I also want this and will take a shot at implementing this in a fork. I'll send in a PR once I'm done.
I think preserving backward compatibility is generally a good idea but I don't want it to prevent us from doing the right thing. I'm fine with current approach you have....
It seems you're using the MongoDB connector. It doesn't support DELETE when the filter cannot be pushed down. In `delete from mongo.admin.sales where emp_id=2 or emp_id=3;` the filter can be...
also re: commit message, consider this suggestion (i.e. describe why the change is being made and what the change is). ``` Add JDBC property to use current catalog in metadata...