[ 
https://issues.apache.org/jira/browse/SOLR-8507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128744#comment-15128744
 ] 

Joel Bernstein commented on SOLR-8507:
--------------------------------------

I think it makes sense to commit this now so since it's working with manual 
testing. Then come back in another ticket and work with the test framework to 
support these calls.

I would like to make one change to the implementation though, which is to call 
only one node to get the version information. Calling each live node could be 
quite a large number of calls with a large cluster.

> Add information about database product name, product version, driver name, 
> and driver version.
> ----------------------------------------------------------------------------------------------
>
>                 Key: SOLR-8507
>                 URL: https://issues.apache.org/jira/browse/SOLR-8507
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrJ
>    Affects Versions: Trunk
>            Reporter: Kevin Risden
>            Priority: Minor
>         Attachments: SOLR-8507.patch, SOLR-8507.patch
>
>
> DBVisualizer asks for information about database product name, product 
> version, driver name, and driver version. These should be implemented in 
> DatabaseMetaDataImpl.
> 2016-01-07 13:30:10.814 FINE    83 [pool-3-thread-10 - E.ᅣチ] RootConnection: 
> DatabaseMetaDataImpl.getDatabaseProductName()
> 2016-01-07 13:30:10.814 FINE    83 [pool-3-thread-10 - E.ᅣチ] RootConnection: 
> DatabaseMetaDataImpl.getDatabaseProductVersion()
> 2016-01-07 13:30:10.814 FINE    83 [pool-3-thread-10 - E.ᅣチ] RootConnection: 
> DatabaseMetaDataImpl.getDriverName()
> 2016-01-07 13:30:10.814 FINE    83 [pool-3-thread-10 - E.ᅣチ] RootConnection: 
> DatabaseMetaDataImpl.getDriverVersion()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to