[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[ https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18546: --- Status: Patch Available (was: Reopened) > BP format does not generate property oozie.service.JPAService.jdbc.url > -- > > Key: AMBARI-18546 > URL: https://issues.apache.org/jira/browse/AMBARI-18546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18546.patch, AMBARI-18546_part2.patch > > > STR: > * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB). > * Notice that oozie-site has config, > {code} > oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name > {code} > E.g., > jdbc:mysql://c6401.ambari.apache.org/oozie > * Export the BP, > api/v1/clusters/c1?format=blueprint > It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a > user trying to use that blueprint will run into errors. > Further, setting the value of that property to > "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it > with the hostname, and it should also dynamically replace the Oozie DB name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[ https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18546: --- Attachment: AMBARI-18546_part2.patch > BP format does not generate property oozie.service.JPAService.jdbc.url > -- > > Key: AMBARI-18546 > URL: https://issues.apache.org/jira/browse/AMBARI-18546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18546.patch, AMBARI-18546_part2.patch > > > STR: > * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB). > * Notice that oozie-site has config, > {code} > oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name > {code} > E.g., > jdbc:mysql://c6401.ambari.apache.org/oozie > * Export the BP, > api/v1/clusters/c1?format=blueprint > It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a > user trying to use that blueprint will run into errors. > Further, setting the value of that property to > "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it > with the hostname, and it should also dynamically replace the Oozie DB name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[ https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18546: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > BP format does not generate property oozie.service.JPAService.jdbc.url > -- > > Key: AMBARI-18546 > URL: https://issues.apache.org/jira/browse/AMBARI-18546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18546.patch > > > STR: > * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB). > * Notice that oozie-site has config, > {code} > oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name > {code} > E.g., > jdbc:mysql://c6401.ambari.apache.org/oozie > * Export the BP, > api/v1/clusters/c1?format=blueprint > It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a > user trying to use that blueprint will run into errors. > Further, setting the value of that property to > "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it > with the hostname, and it should also dynamically replace the Oozie DB name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[ https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18546: --- Attachment: (was: AMBARI-18546.patch) > BP format does not generate property oozie.service.JPAService.jdbc.url > -- > > Key: AMBARI-18546 > URL: https://issues.apache.org/jira/browse/AMBARI-18546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18546.patch > > > STR: > * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB). > * Notice that oozie-site has config, > {code} > oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name > {code} > E.g., > jdbc:mysql://c6401.ambari.apache.org/oozie > * Export the BP, > api/v1/clusters/c1?format=blueprint > It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a > user trying to use that blueprint will run into errors. > Further, setting the value of that property to > "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it > with the hostname, and it should also dynamically replace the Oozie DB name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[ https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18546: --- Attachment: AMBARI-18546.patch > BP format does not generate property oozie.service.JPAService.jdbc.url > -- > > Key: AMBARI-18546 > URL: https://issues.apache.org/jira/browse/AMBARI-18546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18546.patch > > > STR: > * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB). > * Notice that oozie-site has config, > {code} > oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name > {code} > E.g., > jdbc:mysql://c6401.ambari.apache.org/oozie > * Export the BP, > api/v1/clusters/c1?format=blueprint > It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a > user trying to use that blueprint will run into errors. > Further, setting the value of that property to > "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it > with the hostname, and it should also dynamically replace the Oozie DB name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[ https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18546: --- Status: Patch Available (was: Open) > BP format does not generate property oozie.service.JPAService.jdbc.url > -- > > Key: AMBARI-18546 > URL: https://issues.apache.org/jira/browse/AMBARI-18546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18546.patch > > > STR: > * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB). > * Notice that oozie-site has config, > {code} > oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name > {code} > E.g., > jdbc:mysql://c6401.ambari.apache.org/oozie > * Export the BP, > api/v1/clusters/c1?format=blueprint > It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a > user trying to use that blueprint will run into errors. > Further, setting the value of that property to > "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it > with the hostname, and it should also dynamically replace the Oozie DB name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)