refactor(stream): change the encoding of stream consumer group

[Yangsx-1]

The encoding way of stream consumer group is not efficient, this PR changes the encoding according to this discussion.

[PragmaTwice]

Should StreamEntryID::Maximum be {UINT64_MAX - 1, ..} to avoid the -1 case here?

[Yangsx-1]

Can we merge this PR?

[git-hulk]

@Yangsx-1 You can merge PR once the CI passed

[PragmaTwice]

There is one issue that needs to be considered: after the modification, the case where EID MS is -1 needs to be excluded when traversing (iterating) all sub-keys (EID MS|EID SEQ).

As I mentioned here.

[Yangsx-1]

There is one issue that needs to be considered: after the modification, the case where EID MS is -1 needs to be excluded when traversing (iterating) all sub-keys (EID MS|EID SEQ).

As I mentioned here.

It's been changed now.

[PragmaTwice]

Hi @torwig, could you please review this PR when you have some time?

[torwig]

@PragmaTwice Sure. I'll review it today.

[torwig]

@Yangsx-1 @PragmaTwice Since we have UINT64_MAX as a delimiter, should it be an invalid seq of the stream entry ID? Should we consider changing code here, here and here?

[Yangsx-1]

@Yangsx-1 @PragmaTwice Since we have UINT64_MAX as a delimiter, should it be an invalid seq of the stream entry ID? Should we consider changing code here, here and here?

Yes, i'll change these code later.

[sonarqubecloud[bot]]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint