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

Kevin Risden commented on SOLR-8502:
------------------------------------

I think the following four tickets should be addressed. I outlined the reasons 
below:
* SOLR-8507 - This is more about user experience with DBVisualizer. After 
connecting, DBVisualizer displays this info to the user. There is an 
error/warning if this info is not available so hurts user experience.
* SOLR-8508 / SOLR-8510 - Both of these also seem to cause issues with 
DBVisualizer user experience. I haven't narrowed down what parts these are 
absolutely required for, but it would be nice to have them implemented to avoid 
the warnings that DBvisualizer shows.
* SOLR-8521 - Without documentation, using this would not be obvious. Maybe 
this ticket can be addressed after SOLR-8502 is closed?

> Improve Solr JDBC Driver to support SQL Clients like DBVisualizer
> -----------------------------------------------------------------
>
>                 Key: SOLR-8502
>                 URL: https://issues.apache.org/jira/browse/SOLR-8502
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrJ
>    Affects Versions: Trunk
>            Reporter: Kevin Risden
>              Labels: jdbc
>             Fix For: Trunk
>
>         Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Currently when trying to connect to Solr with the JDBC driver with a SQL 
> client the driver must implement more methods and metadata to allow 
> connections. This JIRA is designed to act as an umbrella for the JDBC changes.
> An initial pass from a few months ago is here: 
> https://github.com/risdenk/lucene-solr/tree/expand-jdbc. This needs to be 
> broken up and create patches for the related sub tasks.



--
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