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

Hadoop QA commented on AMBARI-16207:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12801788/AMBARI-16207.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  org.apache.ambari.server.agent.TestHeartbeatHandler

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6753//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6753//console

This message is automatically generated.

> 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
>
>         Attachments: AMBARI-16207.patch
>
>
> 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)

Reply via email to