[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations
[ https://issues.apache.org/jira/browse/AMBARI-23456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734527#comment-16734527 ] Hudson commented on AMBARI-23456: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #88 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/88/]) AMBARI-23456. Fix typos. (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=f5074e7a24407abca08c0a2d95db1f14daa2b267]) * (edit) README.md * (edit) docs/index.md * (edit) docs/development.md > Log Search: generate mardown docs for properties and logfeeder configs based > on annotations > --- > > Key: AMBARI-23456 > URL: https://issues.apache.org/jira/browse/AMBARI-23456 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations
[ https://issues.apache.org/jira/browse/AMBARI-23456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23456. --- Resolution: Fixed > Log Search: generate mardown docs for properties and logfeeder configs based > on annotations > --- > > Key: AMBARI-23456 > URL: https://issues.apache.org/jira/browse/AMBARI-23456 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations
[ https://issues.apache.org/jira/browse/AMBARI-23456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734450#comment-16734450 ] Hudson commented on AMBARI-23456: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #87 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/87/]) AMBARI-23456. Add developement guide markdowns & remove some old docs (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=1deed01e48015519c3e566762f53e2e5a38bb3eb]) * (delete) ambari-logsearch-server/README.md * (edit) docs/development.md * (edit) README.md * (delete) ambari-logsearch-logfeeder/README.md > Log Search: generate mardown docs for properties and logfeeder configs based > on annotations > --- > > Key: AMBARI-23456 > URL: https://issues.apache.org/jira/browse/AMBARI-23456 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24872) NIFI-Hosts dashboard does not show any metrics in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-24872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-24872: -- Assignee: Aravindan Vijayan > NIFI-Hosts dashboard does not show any metrics in Grafana > - > > Key: AMBARI-24872 > URL: https://issues.apache.org/jira/browse/AMBARI-24872 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: amarnath reddy pappu >Assignee: Aravindan Vijayan >Priority: Critical > > Description > In Grafana, NIFI-Hosts dashboard does not show any metrics though data > present in the AMS. > Steps to reproduce it > 1. Install the cluster the and add NIFI service. > 2. Goto NIFI and add Ambari reporting task so that it sends the metrics to > AMS. > 3. You can see NIFI-Home shows the Graphs but NIFI-Hosts does not. > Below API call returns the data points > http://xxx:6188/ws/v1/timeline/metrics?metricNames=jvm.uptime._avg=nifi==1541611634=1541698034 > where as with hostname clause it does not return any > http://xxx:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=jvm.uptime._avg=%=nifi==1541611634=1541698034=20=avg=false > NIFI is sending instanceid and but AMS is not handling correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25089) NIFI-Hosts dashboard does not show any metrics in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-25089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25089: Labels: pull-request-available (was: ) > NIFI-Hosts dashboard does not show any metrics in Grafana > - > > Key: AMBARI-25089 > URL: https://issues.apache.org/jira/browse/AMBARI-25089 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25089) NIFI-Hosts dashboard does not show any metrics in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-25089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-25089. Resolution: Duplicate > NIFI-Hosts dashboard does not show any metrics in Grafana > - > > Key: AMBARI-25089 > URL: https://issues.apache.org/jira/browse/AMBARI-25089 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25083) Log Search: fallback to use dynamic field 'ws_*' if new field name contains whitespace
[ https://issues.apache.org/jira/browse/AMBARI-25083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-25083. --- Resolution: Fixed > Log Search: fallback to use dynamic field 'ws_*' if new field name contains > whitespace > -- > > Key: AMBARI-25083 > URL: https://issues.apache.org/jira/browse/AMBARI-25083 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25088) Enable Kerberos fails when Ambari server is not on a registered host
[
https://issues.apache.org/jira/browse/AMBARI-25088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734228#comment-16734228
]
Hudson commented on AMBARI-25088:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10413 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10413/])
[AMBARI-25088] Enable Kerberos fails when Ambari server is not on a (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=77b5319381fd083f4f9774581b1fad082bb71e4a])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
> Enable Kerberos fails when Ambari server is not on a registered host
>
>
> Key: AMBARI-25088
> URL: https://issues.apache.org/jira/browse/AMBARI-25088
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Enable Kerberos fails when Ambari server is not on a registered host.
> The following error is seen in /var/log/ambari-server.log
> {noformat}
> 2019-01-03 15:28:34,238 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: org.apache.ambari.server.HostNotFoundException:Host not
> found, hostname=c7401.ambari.apache.org
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=c7401.ambari.apache.org
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:190)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:174)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2431)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
> at com.sun.proxy.$Proxy134.findConfigurationTagsWithOverrides(Unknown
> Source)
> at
> org.apache.ambari.server.state.ConfigHelper.calculateExistingConfigurations(ConfigHelper.java:2158)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.calculateConfigurations(KerberosHelperImpl.java:1722)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.getActiveIdentities(KerberosHelperImpl.java:1797)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.calculateServiceIdentities(KerberosServerAction.java:512)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:456)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This is caused when Ambari tried to find the host-specific configuration
> values when processing the Kerberos identities and the host is not registered
> for the relevant cluster. This can happen when the Ambari server Kerberos
> identity is being processed when the Ambari server host is not registered
> with the cluster.
> To solve this, host specific configuration values should not be obtained for
> the non-registered Ambari server host.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25028) [Log Search UI] Populate `Component Name` in validator
[ https://issues.apache.org/jira/browse/AMBARI-25028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25028: --- Status: Patch Available (was: Open) > [Log Search UI] Populate `Component Name` in validator > -- > > Key: AMBARI-25028 > URL: https://issues.apache.org/jira/browse/AMBARI-25028 > Project: Ambari > Issue Type: Sub-task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 6h > Time Spent: 10m > Remaining Estimate: 5h 50m > > Populate the `component name` field in validator when it is available from > the configuration object. > If more than component is available populate with the first one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25028) [Log Search UI] Populate `Component Name` in validator
[ https://issues.apache.org/jira/browse/AMBARI-25028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25028: Labels: pull-request-available (was: ) > [Log Search UI] Populate `Component Name` in validator > -- > > Key: AMBARI-25028 > URL: https://issues.apache.org/jira/browse/AMBARI-25028 > Project: Ambari > Issue Type: Sub-task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 6h > Remaining Estimate: 6h > > Populate the `component name` field in validator when it is available from > the configuration object. > If more than component is available populate with the first one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25088) Enable Kerberos fails when Ambari server is not on a registered host
[
https://issues.apache.org/jira/browse/AMBARI-25088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-25088:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Enable Kerberos fails when Ambari server is not on a registered host
>
>
> Key: AMBARI-25088
> URL: https://issues.apache.org/jira/browse/AMBARI-25088
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Enable Kerberos fails when Ambari server is not on a registered host.
> The following error is seen in /var/log/ambari-server.log
> {noformat}
> 2019-01-03 15:28:34,238 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: org.apache.ambari.server.HostNotFoundException:Host not
> found, hostname=c7401.ambari.apache.org
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=c7401.ambari.apache.org
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:190)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:174)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2431)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
> at com.sun.proxy.$Proxy134.findConfigurationTagsWithOverrides(Unknown
> Source)
> at
> org.apache.ambari.server.state.ConfigHelper.calculateExistingConfigurations(ConfigHelper.java:2158)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.calculateConfigurations(KerberosHelperImpl.java:1722)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.getActiveIdentities(KerberosHelperImpl.java:1797)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.calculateServiceIdentities(KerberosServerAction.java:512)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:456)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This is caused when Ambari tried to find the host-specific configuration
> values when processing the Kerberos identities and the host is not registered
> for the relevant cluster. This can happen when the Ambari server Kerberos
> identity is being processed when the Ambari server host is not registered
> with the cluster.
> To solve this, host specific configuration values should not be obtained for
> the non-registered Ambari server host.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25086) Upgrading Using a Modified Default Version Repository Fails on Some Services
[ https://issues.apache.org/jira/browse/AMBARI-25086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734158#comment-16734158 ] Hudson commented on AMBARI-25086: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10412 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10412/]) [AMBARI-25086] Upgrading Using a Modified Default Version Repository (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c20e418a2c0d278db6dea9caa5fd45cf6c80723d]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/repository/VersionDefinitionTest.java > Upgrading Using a Modified Default Version Repository Fails on Some Services > > > Key: AMBARI-25086 > URL: https://issues.apache.org/jira/browse/AMBARI-25086 > Project: Ambari > Issue Type: Task >Affects Versions: 2.7.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When performing a stack upgrade, if the user chooses the "Default Version > Definition" option and just modifies the default URLs, the backing VDF which > is created and stored in the database contains which do not support > upgrading. > Before the upgrade, if any of these services are in maintenance mode (such as > Ambari Infra), they will prevent the upgrade from starting. > During the actual upgrade, this will cause problems on finalization as those > services/components have not participated, yet the VDF indicates that they > should have. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25089) NIFI-Hosts dashboard does not show any metrics in Grafana
Aravindan Vijayan created AMBARI-25089: -- Summary: NIFI-Hosts dashboard does not show any metrics in Grafana Key: AMBARI-25089 URL: https://issues.apache.org/jira/browse/AMBARI-25089 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.3 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25086) Upgrading Using a Modified Default Version Repository Fails on Some Services
[ https://issues.apache.org/jira/browse/AMBARI-25086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-25086. -- Resolution: Fixed > Upgrading Using a Modified Default Version Repository Fails on Some Services > > > Key: AMBARI-25086 > URL: https://issues.apache.org/jira/browse/AMBARI-25086 > Project: Ambari > Issue Type: Task >Affects Versions: 2.7.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When performing a stack upgrade, if the user chooses the "Default Version > Definition" option and just modifies the default URLs, the backing VDF which > is created and stored in the database contains which do not support > upgrading. > Before the upgrade, if any of these services are in maintenance mode (such as > Ambari Infra), they will prevent the upgrade from starting. > During the actual upgrade, this will cause problems on finalization as those > services/components have not participated, yet the VDF indicates that they > should have. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25084) Delete identities fails when removing service in reverse order
[
https://issues.apache.org/jira/browse/AMBARI-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733968#comment-16733968
]
Hudson commented on AMBARI-25084:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10411 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10411/])
AMBARI-25084. Delete identities fails when removing service in reverse (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ecce21178c9f3612dca8354b9874e16ec7702078])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterDAO.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/ServiceConfigDAOTest.java
> Delete identities fails when removing service in reverse order
> --
>
> Key: AMBARI-25084
> URL: https://issues.apache.org/jira/browse/AMBARI-25084
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> (reverse order = host components first, then components, then service)
> STR:
> Install ZooKeeper + Kafka + Kerberos
> Stop Kafka
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts/c7401.ambari.apache.org/host_components/KAFKA_BROKER
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA/components/KAFKA_BROKER
> => identities are removed
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA
> => identity removal fails with PersistenceException
> {code}
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.6.2.v20151217-774c696):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
>
