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.

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

Feature: HEAD collection name should be configurable #1254

Closed
egasimov opened this issue Jan 17, 2023 · 3 comments
Closed

Feature: HEAD collection name should be configurable #1254

egasimov opened this issue Jan 17, 2023 · 3 comments
Labels

Comments

@egasimov
Copy link
Contributor

Is your feature request related to a problem? Please describe.
There is no option to configure the collection name of the jv_head_id. So if multiple microservices are writing in multiple collections in that database all services are using the same jv_head_id.

Describe the solution you'd like
Make it configurable which collection name should be used

Describe alternatives you've considered
none

Additional context
There was an similar ticket but with making SNAPSHOT COLLECTION configurable, #1169, and already merged.

P:S I would like to contribute by creating an pull request.

@egasimov
Copy link
Contributor Author

egasimov commented Jan 17, 2023

Hey @bartoszwalacik! I have just made PR for feature described above, could you please review and share your thoughts, whenever have time?

@mmushfiq
Copy link

I would also appreciate having this feature available. After that, we can use it.

@egasimov egasimov changed the title HEAD collection name should be configurable Feature: HEAD collection name should be configurable Jan 25, 2023
@bartoszwalacik
Copy link
Member

released in 6.9.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants