You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hao Hao (JIRA)" <ji...@apache.org> on 2016/12/14 02:19:58 UTC

[jira] [Updated] (SENTRY-1538) Create schema for storing HMS notifications

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

Hao Hao updated SENTRY-1538:
----------------------------
    Status: Patch Available  (was: Open)

> Create schema for storing HMS notifications
> -------------------------------------------
>
>                 Key: SENTRY-1538
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1538
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>            Assignee: Hao Hao
>             Fix For: sentry-ha-redesign
>
>         Attachments: SENTRY-1538.001-sentry-ha-redesign.patch
>
>
> As HMS Follower processes HMS notifications, they should be stored in Sentry DB. At a minimum we can only store notification ID, but for debugging/troubleshooting it is better to store actual JSON notification events as well.
> So this task about adding a schema for storing notifications. It its simplest form it will contain just notification ID as the primary key, possibly timestamp and the JSON notification event.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)