Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow BigInt/Buffer to be used as initialSequenceId and/or sequenceId #124

Open
alanhoff opened this issue Sep 23, 2020 · 0 comments · May be fixed by #127
Open

Allow BigInt/Buffer to be used as initialSequenceId and/or sequenceId #124

alanhoff opened this issue Sep 23, 2020 · 0 comments · May be fixed by #127
Labels
triage/week-40 type/feature

Comments

@alanhoff
Copy link
Contributor

Hello there,

Right now the producer's sequence ID is limited to 4 bytes here:

However we could allow 8 bytes integers if we allow producer/message to receive a BigInt and/or a 8 bytes buffer.

I'm trying to match a dataset that uses 8 bytes integers for keys as my sequence ID, that's why I found this limitation :-)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage/week-40 type/feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feature: allow messages and producers to handle int64 sequences alanhoff/pulsar-client-node
2 participants
@alanhoff @sijie