You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/07/14 22:43:00 UTC

[jira] [Resolved] (SENTRY-1848) Separate legacy sentry configs from sentry ha configs for api compatibility

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

Na Li resolved SENTRY-1848.
---------------------------
    Resolution: Won't Fix

sentry-ha-redesign will be sentry 2.0. We don't need to maintain the compatibility.

> Separate legacy sentry configs from sentry ha configs for api compatibility
> ---------------------------------------------------------------------------
>
>                 Key: SENTRY-1848
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1848
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Na Li
>            Assignee: Na Li
>             Fix For: sentry-ha-redesign
>
>
> sentry.service.client.server.rpc-address has been overloaded with ha awareness which breaks legacy compatibility.
> we'll need to keep the legacy format, and add a new ha setting. The new HA aware sentry client should read the new ha setting



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