You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2016/05/02 20:18:12 UTC
[jira] [Updated] (AMBARI-16207) Provide Ability To Pass JPA /
EclipseLink Properties to the DataSource
[ https://issues.apache.org/jira/browse/AMBARI-16207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-16207:
-------------------------------------
Status: Patch Available (was: Open)
> Provide Ability To Pass JPA / EclipseLink Properties to the DataSource
> ----------------------------------------------------------------------
>
> Key: AMBARI-16207
> URL: https://issues.apache.org/jira/browse/AMBARI-16207
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.4.0
>
>
> There is currently no way to pass JPA or EclipseLink specific connection/DataSource properties in from {{ambari.properties}}. Although there exists {{Configuration.getDatabaseCustomProperties}}, these are actually _driver specific_ properties and not properties for EclipseLink.
> For example, if I wanted to pass in to the JDBC Driver {{foo=bar}}, then I could set
> {{server.jdbc.properties.foo=bar}} and this will get translated into {{eclipselink.jdbc.property.foo=bar}}.
> However, if I wanted to set any of the EclipseLink or JPA specific DataSource properties (see http://www.eclipse.org/eclipselink/api/2.6/org/eclipse/persistence/config/PersistenceUnitProperties.html) I would not be able to.
> Proposal is to add something similar to the custom driver properties:
> {code}
> server.persistence.properties.eclipselink.jdbc.batch-writing.size=25
> {code}
> Which could get translated into
> {code}
> properties.put("eclipselink.jdbc.batch-writing.size", 25)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)