[jira] [Commented] (BOOKKEEPER-433) Validate subscriber id for subscription

["Stu Hood (JIRA)" <ji...@apache.org>]

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

Stu Hood commented on BOOKKEEPER-433:
-------------------------------------

IMO, rather than validating the subscriber id, it might be good to think about how we can accept arbitrary binary subscriber ids without colliding with private/internal subscriber ids. Technically, subscriber ids can already contain arbitrary bytes (ByteString), so internally namespacing or marking private/internal subscriber ids in some way makes more sense to me (as suggested on the [other ticket|https://issues.apache.org/jira/browse/BOOKKEEPER-422?focusedCommentId=13473538&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13473538].)
                
> Validate subscriber id for subscription
> ---------------------------------------
>
>                 Key: BOOKKEEPER-433
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-433
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-server
>    Affects Versions: 4.2.0
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.2.0
>
>
> currently we don't validate the topic and the subscriber id when subscription. we need to validate it since we prefix underscore for a subscriber to indicate it is a remote subscriber.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira