GitHub user haoch opened a pull request: https://github.com/apache/incubator-eagle/pull/476
[EAGLE-591][WIP] Fix conflict streamId between different sites while installing 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`. You can merge this pull request into a Git repository by running: $ git pull https://github.com/haoch/incubator-eagle FixConflictStreamId Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/476.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #476 ---- commit de42e6ab6a0140b5177c39439c224c1ae0d39854 Author: Hao Chen <h...@apache.org> Date: 2016-10-08T03:04:55Z Fix conflict streamId between different sites while installing ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---