There are multiple JDBC clients that require a PreparedStatement to work.
SolrJ JDBC - Ensure that Spark works with SolrJ JDBC
Implement PreparedStatementImpl parameterization
SolrJ JDBC - Ensure that Python JayDeBeApi works with SolrJ JDBC
SolrJ JDBC - Ensure that an ODBC-JDBC bridge works with SolrJ JDBC
Joel Bernstein - Here is a patch and test.
Added implementation of PreparedStatement.execute()
Joel Bernstein - Is this minor enough to get into Solr 6? Since JDBC isn't released yet and should be minimal impact.
Some more thought needs to go into this due to PreparedStatement being special and not all methods being supported if its a PreparedStatement.
Patch that implements ConnectionprepareStatement. Adds PreparedStatementImpl and tests to JdbcTest
Think the latest patch is good to go. Joel Bernstein - can you take a peek?
Yep, I'll take a look
Looks good. It doesn't yet do the parameter substitution I believe. Should be pretty straight forward to add that in separate ticket though.
Correct no parameter substitution yet. The problem I am trying to solve with this is avoid the NPE that gets thrown when clients try to connect to move on to the next NPE clients throw when first connecting. Parameter substitution definitely should be added and shouldn't be too bad to do in a separate JIRA.
+1 to commit
Commit 221ecfa89821665d69f55ed1b3502f50b3698720 in lucene-solr's branch refs/heads/master from Kevin Risden
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=221ecfa ]
SOLR-8809: Implement Connection.prepareStatement
Commit 6276fe5ec7bcbdd30e30059391707084b9c8e989 in lucene-solr's branch refs/heads/branch_6x from Kevin Risden
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6276fe5 ]