You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Chad Roberts (JIRA)" <ji...@apache.org> on 2013/10/24 18:25:02 UTC
[jira] [Commented] (AMBARI-3585) Allow the SQLite.JDBCDriver to
load as an alternative to org.sqlite.jdbc
[ https://issues.apache.org/jira/browse/AMBARI-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804358#comment-13804358 ]
Chad Roberts commented on AMBARI-3585:
--------------------------------------
This seems like a very sane thing to do.
+1 to the patch.
> Allow the SQLite.JDBCDriver to load as an alternative to org.sqlite.jdbc
> ------------------------------------------------------------------------
>
> Key: AMBARI-3585
> URL: https://issues.apache.org/jira/browse/AMBARI-3585
> Project: Ambari
> Issue Type: Improvement
> Components: controller
> Affects Versions: 1.4.1
> Environment: Fedora/RHEL
> Reporter: Trevor McKay
> Assignee: Trevor McKay
> Attachments: sqlite.patch
>
>
> On Fedora/RHEL/CentOS, the javasqlite JDBC driver is packaged as part of the base system while the xerial sqlite-jdbc driver is not.
> To facilitate packaging in Fedora and maintain current behavior for rpms built via maven, allow SQLiteConncetionFactory to load the "SQLite.JDBCDriver" class if loading "org.sqlite.jdbc" fails.
> If both fail, report the original exception (class not found for org.sqlite.jdbc)
--
This message was sent by Atlassian JIRA
(v6.1#6144)