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

Dennis Gove updated SOLR-8479:
------------------------------
    Attachment: SOLR-8479.patch

This is a first pass at the JDBCStream. There are still open questions and 
unimplemented pieces but I'm putting this out there to start the conversation. 
No tests are included.

1. Currently it's handling the loading of JDBC Driver classes by requiring the 
driver class be provided and will then call 
{code}
Class.forName(driverClassName);
{code}
during open(). I'm wondering if there's a better way to handle this, 
particularly if we can do the loading via config file handling.

> Add JDBCStream for integration with external data sources
> ---------------------------------------------------------
>
>                 Key: SOLR-8479
>                 URL: https://issues.apache.org/jira/browse/SOLR-8479
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrJ
>            Reporter: Dennis Gove
>            Priority: Minor
>         Attachments: SOLR-8479.patch
>
>
> Given that the Streaming API can merge and join multiple incoming SolrStreams 
> to perform complex operations on the resulting combined datasets I think it 
> would be beneficial to also support incoming streams from other data sources. 
> The JDBCStream will provide a Streaming API interface to any data source 
> which provides a JDBC driver.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to