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

Puneet Gupta edited comment on LENS-123 at 10/7/15 1:35 PM:
------------------------------------------------------------

What about default driver properties ? 
As of now the default files are in the jar and are not meant to me modified by 
users . 

If we are supporting multiple drivers, the user may need to change some of the 
default driver properties  (say connection timeout or pool size for all JDBC 
drivers) for all drivers of that type. 

Should we move these default property files to respective driver type folder ( 
example Drivers/hive and Drivers/jdbc) ?
We can also think about having driver class name in default file in that case. 




was (Author: puneet884):
What about default driver properties ? 
As of now the default files are in the jar and are not meant to me modified by 
users . 

If we are supporting multiple drivers, the user may need to change some of the 
default driver properties  (say connection timeout or pool size for all JDBC 
drivers) for all drivers of that type. 

Should we move these default property files to respective driver type folder ( 
example Drivers/hive and Drivers/jdbc) ?



> Ability to load different instances of same driver class
> --------------------------------------------------------
>
>                 Key: LENS-123
>                 URL: https://issues.apache.org/jira/browse/LENS-123
>             Project: Apache Lens
>          Issue Type: New Feature
>          Components: server
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Puneet Gupta
>              Labels: Hackathon-July
>
> Currently we are loading only one driver instance per class. We should be 
> able to load multiple different instances of a driver class.
> For example, There can be multiple HiveDrivers talking to different 
> HiveServers sitting on each colo. Or different JDBCDrivers talking to 
> different dbs.



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

Reply via email to