You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/03/23 17:06:00 UTC

[jira] [Commented] (KNOX-2302) Skip re-deployment of generated topology if the topology has not changed

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

ASF subversion and git services commented on KNOX-2302:
-------------------------------------------------------

Commit 3d17ede66d29ccf41e95c469e56c696f99262df5 in knox's branch refs/heads/master from Philip Zampino
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=3d17ede ]

KNOX-2301 and KNOX-2302 (#297)

* KNOX-2301 - Trigger discovery for descriptors at gateway start time

* KNOX-2302 - Skip re-deployment of generated topology if the topology has not changed

> Skip re-deployment of generated topology if the topology has not changed
> ------------------------------------------------------------------------
>
>                 Key: KNOX-2302
>                 URL: https://issues.apache.org/jira/browse/KNOX-2302
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 1.4.0
>            Reporter: Philip Zampino
>            Assignee: Philip Zampino
>            Priority: Major
>
> Knox discovery +always+ writes generated topologies to disk, triggering [re]deployment of that topology. It would be better to compare the generated topology against the already-deployed version (if it exists) prior to writing it to disk. If the generated version is the same as the already-deployed version, then the newly-generated topology should be discarded, so the re-deployment will be skipped.



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