[
https://issues.apache.org/jira/browse/SOLR-14154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006230#comment-17006230
]
Kevin Risden commented on SOLR-14154:
-------------------------------------
[~vercani] can you provide a PR for this? Should be a simple change. Mostly
just should implement get/set here [1] at the same time following the
Connection javadocs [2]
I am curious about what SQL client is running into this. For reference, the
database metadata itself shows no support for transactions [3] and [4].
[1]
https://github.com/apache/lucene-solr/blob/master/solr/solrj/src/java/org/apache/solr/client/solrj/io/sql/ConnectionImpl.java#L188
[2]
https://docs.oracle.com/javase/8/docs/api/java/sql/Connection.html#getTransactionIsolation--
[3]
https://github.com/apache/lucene-solr/blob/master/solr/solrj/src/java/org/apache/solr/client/solrj/io/sql/DatabaseMetaDataImpl.java#L672
[4]
https://docs.oracle.com/javase/8/docs/api/java/sql/DatabaseMetaData.html#supportsTransactionIsolationLevel-int-
> Return correct isolation level when retrieving it from the SQL Connection
> -------------------------------------------------------------------------
>
> Key: SOLR-14154
> URL: https://issues.apache.org/jira/browse/SOLR-14154
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Parallel SQL
> Affects Versions: 8.4
> Reporter: Nick Vercammen
> Priority: Minor
> Fix For: master (9.0)
>
>
> When calling the getTransactionIsolation() on the Sql.ConnectionImpl an
> UnsupportedException is thrown. It would be better to return TRANSACTION_NONE
> so clients can determine themselves it is not supported without receiving an
> exception
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
