[
https://issues.apache.org/jira/browse/AMBARI-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804450#comment-13804450
]
Trevor McKay commented on AMBARI-3585:
--------------------------------------
Hmm, I am not convinced that the sqlite stuff is even used. Default seems to
be derby and postgres. Do we need it at all? Should we remove
JDBCProviderModule, DBHelper, and SQLiteConnectionFactory?
> 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)
