You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Ryan McKinley (JIRA)" <ji...@apache.org> on 2007/11/18 22:08:43 UTC

[jira] Commented: (SOLR-373) Build a JDBC driver to access Solr

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

Ryan McKinley commented on SOLR-373:
------------------------------------

What do you see as the value for a JDBC driver?  Are there good examples of packages that would "just work" if solr had a JDBC driver?

Beyond a toy examples, stuffing a solr response into rows/columns will get very limiting very fast.  

> Build a JDBC driver to access Solr
> ----------------------------------
>
>                 Key: SOLR-373
>                 URL: https://issues.apache.org/jira/browse/SOLR-373
>             Project: Solr
>          Issue Type: New Feature
>          Components: search, update
>            Reporter: Thomas Peuss
>            Priority: Minor
>
> Hello!
> Would it be a good thing to have a JDBC driver to access Solr? This would help people only knowing SQL syntax. And you can use things like Hibernate on top of that. Maybe this is a good alternative to Solrj. In the first run I would not allow any joins.
> I think of a SQL syntax like
> SELECT * FROM SOLR WHERE name='Albert' OR name='Einstein'
> which gets translated to a Solr query like
> q=name:Albert OR name:Einstein&fl=*
> What do you think?
> CU
> Thomas

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.