[
https://issues.apache.org/jira/browse/SOLR-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809393#comment-16809393
]
Joel Bernstein edited comment on SOLR-13220 at 4/4/19 12:22 AM:
----------------------------------------------------------------
The security implications of the connect was too complex. Having the jdbc
stream lazily cache connections ensures that each jdbc call passes in the
credentials, rather then grabs an insecure handle to a connection.
The next release of the zeppelin-solr interpreter will allow you to configure a
default JDBC connection and will add the connection info to the outgoing jdbc
expression so users don't need to know or send a connection each time.
This gives us the best scenario I think:
1) Secure connections
2) Cached connections
3) A client can choose to add the connection info to the jdbc expression so
users don't have to know or deal with the connection info on each call.
was (Author: joel.bernstein):
The security implications of the connect was too complex. Having the jdbc
stream lazily cache connections ensures that each jdbc call passes in the
credentials, rather then grabs an insecure handle to a connection.
The next release of the zeppelin-solr interpreter will allow you to configure a
default JDBC connection and will add the connection info to the outgoing jdbc
expression so users don't need to know or send a connection each time.
This give us the best scenario I think:
1) Secure connections
2) Cached connections
3) A client can choose to add the connection info to the jdbc expression so
users don't have to know or deal with the connection info on each call.
> Add connect Streaming Expression to create cached JDBC connections
> ------------------------------------------------------------------
>
> Key: SOLR-13220
> URL: https://issues.apache.org/jira/browse/SOLR-13220
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Joel Bernstein
> Assignee: Joel Bernstein
> Priority: Major
>
> Currently the *jdbc* Streaming Expression requires that username, password
> and URL parameters are set to operate. This ticket will allow users to
> configure JDBC connections using the new *connect* Streaming Expression.
> The *jdbc* Streaming Expression will be changed to use the cached connections
> rather than accepting parameters directly.
> The *parallel* Streaming Expression can be used to setup connections on each
> node of a collection.
> The *Apache Hive* JDBC driver will also be included with Apache Solr as part
> of this ticket to allow seamless out-of-the-box connection to Apache Hive.
> Syntax:
> {code:java}
> connect(connectionName, url="", username="", password=""){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
