[ https://issues.apache.org/jira/browse/EAGLE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15557065#comment-15557065 ]
ASF GitHub Bot commented on EAGLE-591: -------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/476 > Fix conflict streamId between different sites when installation > --------------------------------------------------------------- > > Key: EAGLE-591 > URL: https://issues.apache.org/jira/browse/EAGLE-591 > Project: Eagle > Issue Type: Bug > Affects Versions: v0.5.0 > Reporter: Hao Chen > Assignee: Hao Chen > Fix For: v0.5.0 > > > Eagle alert engine currently only support global-unique streamId (where a > "stream" in fact means a physicla data source with schema), but it's common > use case the different sites may have same-kind (same stream schema) of > streams especially when installing same app into different sites, so we > should refactor the alert engine metadata to support such kinds of use cases. > This ticket will only fix conflict streamId between different sites when > installation as a quick solution by simply using "{streamId}_{siteId}" as the > physical installed "streamId". -- This message was sent by Atlassian JIRA (v6.3.4#6332)