You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2019/11/20 14:57:00 UTC

[jira] [Commented] (AMBARI-25415) AMS - metadata table has incorrect primary key

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

Hudson commented on AMBARI-25415:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #612 (See [https://builds.apache.org/job/Ambari-branch-2.7/612/])
AMBARI-25415 AMS - metadata table has incorrect primary key (mpapirkovskyy: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a41f66c19e2c80fce34ca334b3a9a45466d770d0])
* (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/ambari/metrics/core/timeline/query/PhoenixTransactSQL.java


> AMS - metadata table has incorrect primary key
> ----------------------------------------------
>
>                 Key: AMBARI-25415
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25415
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-metrics
>    Affects Versions: 2.7.5
>            Reporter: Ihor Lukianov
>            Assignee: Ihor Lukianov
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.5
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> The metrics metadata table has incorrect PK, which causes some metadata information to be overridden by false metrics that appear due to some other issue



--
This message was sent by Atlassian Jira
(v8.3.4#803005)