ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallav Kulshreshtha (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-22089) Hive View 2.0 - Unable to update existing saved queries, view creates new records under saved queries tab
Date Thu, 28 Sep 2017 19:44:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pallav Kulshreshtha updated AMBARI-22089:
-----------------------------------------
    Attachment: AMBARI-22089_branch-trunk.patch

> Hive View 2.0 - Unable to update existing saved queries, view creates new records under
saved queries tab
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22089
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22089
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>            Reporter: Pallav Kulshreshtha
>            Assignee: Pallav Kulshreshtha
>            Priority: Blocker
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-22089_branch-trunk.patch
>
>
> Under the "Saved Queries" section in Ambari, there exist multiple entries for the query
- all entries have the same query name, that is - when changes are made to a query and subsequently
saved, an entry gets created. 
> However, all entries have the same name - after a while it is not possible to know which
is the latest version. 
> The "Saved Queries" view does not include a timestamp nor does it automatically append
a version name to the query - thus making it hard for the user to figure out which is the
latest query 
> Review the screenshot in attached adobe pdf
> Issue: In Hive view2.0 - when query is saved it gets saved with the provided name say
"test-query1" - now go to "Saved queries" tab and click on "test-query1" and modify the query
and then do save as again - in this case instead of overriding (updating) the saved query
it creates one more copy with same name. this is creating a confusion which one is the latest
one as there is no timestamps.
> One more thing is - while saving the query - if I give existing saved query name then
also it is creating one more copy with same name.
> In Hive view1.5 - it overrides the query name with note saying as "Saving will overwrite
previously saved query" .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message