Skip to content

[RIP-26] [Feature] Both CQ and BCQ need to be supported in DefaultMessageStore. #3708

Closed

Description

@Erik1288

The issue tracker is ONLY used for bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.

Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.

Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:

FEATURE REQUEST

  1. Please describe the feature you are requesting.
    Both CQ and BCQ need to be supported in DefaultMessageStore.

  2. Provide any additional detail on your proposed use case for this feature.

  • ). Remove StreamMessageStore
  • ). Make DefaultMessageStore support both BCQ and CQ.
  1. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

  2. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

  • [Refactor CQ and BCQ loading process]: unify loading process.
  • [add CorrectLogicOffsetService): add CorrectLogicOffsetService to periodically correct min logic offset.

Activity

  1. Git-Yang commented on Jan 5, 2022

    @Git-Yang
    Member

    Link #3704

  2. vongosling commented on Jan 6, 2022

    @vongosling
    Member

    @Git-Yang You could link it in the pr. Actually, pr and issue are mutually linked if you notice the GitHub toolbar on the right side.

  3. added 3 commits that reference this issue on Jan 6, 2022
  4. RongtongJin commented on Jan 13, 2022

    @RongtongJin
    Contributor

    All Merged

  5. added 3 commits that reference this issue on Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions