[ 
https://issues.apache.org/jira/browse/SOLR-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Risden updated SOLR-8786:
-------------------------------
    Attachment: 
zeppelin-0.6.0-incubating-SNAPSHOT_solr-7.0.0-SNAPSHOT_20160307.pdf
                Solr JDBC Test.json

[~joel.bernstein] - Apache Zeppelin already seems to work with the Solr JDBC 
driver. I attached the notebook json and a pdf of the printout from the run 
notebook. The charts and graphs work well too. 

The one thing that isn't intuitive is that you can't have a semicolon at the 
end of the statement. This causes the following exception:

{code}
Caused by: java.io.IOException: --> 
http://default.attlocal.net:8983/solr/test_shard1_replica1/:line 1:33: 
extraneous input ';' expecting <EOF>
{code}

The other weird thing I found was that "select * from test limit 10" doesn't 
seem to work. This causes the following exception:

{code}
Caused by: java.io.IOException: --> 
http://default.attlocal.net:8983/solr/test_shard1_replica1/:Select columns must 
be specified.
{code}

The error message for each of those is "Couldn't read first tuple" so that 
needs to be improved. It would be great to improve that error message before 
6.0 goes out.

> Ensure Solr's JDBC Driver works with Apache Zeppelin
> ----------------------------------------------------
>
>                 Key: SOLR-8786
>                 URL: https://issues.apache.org/jira/browse/SOLR-8786
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Joel Bernstein
>         Attachments: Solr JDBC Test.json, 
> zeppelin-0.6.0-incubating-SNAPSHOT_solr-7.0.0-SNAPSHOT_20160307.pdf
>
>
> There is already a ticket open to improve the JDBC driver to work with more 
> clients, but I'd like to make a special ticket for Apache Zeppelin. 



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