This will use the functionality from #4338.
@nahi is working on this.
Spark also requires this PreparedStatement support when using presto-jdbc.
@nahi Are you still working on this?
@electrum Really sorry for late reply. I created this commit months ago but due to work commitments I didn't have enough time to write unit tests after that. https://github.com/treasure-data/presto/commit/9b042eec34fbc3ee679d9fee992b5c684b1c8bc8
It's already out-of-sync with current master branch but do you think it's worth trying to rebase?
We still need this feature, so please do! The JDBC driver hasn't had many changes so it's likely the rebase conflicts are minimal.
@electrum @nahi - Looks like this is very close. What would it take to get this to the finish line? Thanks.
We are using PDI/Kettle/Spoon ... it would be very nice to have prepared statements in the presto jdbc driver, because otherwise spoon cannot get the metadata for the result set of an SQL statement, ie. it cannot explore and show, which fields and types the SQL statement will return ... it does this by preparing the SQL statement and then asking for DESCRIBE OUTPUT of the query ... so it would know, which fields the SQL statement would return ... any chances to see prepared statements in presto?
Has anyone had luck getting this working? Nahi's solution is nearly a year out of sync with master... is anyone still pursuing this? It would be great to have JDBC support for applications like PDI/Pentaho or Snaplogic.
Currently prepared statements are supported by JDBC simba drivers which work with Teradata provided release of Presto.
So we can use https://www.simba.com/drivers/presto-odbc-jdbc/ simba jdbc drivers here? We can integrate spark to Presto. Right?
Any updates?
+1
When can this function be completed?
I finished up @nahi's patch: #10673
+1
Very needed indeed
Most helpful comment
+1
Very needed indeed