-
Notifications
You must be signed in to change notification settings - Fork 344
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
Custom id in collection #1755
Comments
@SimoneLazzaris are you sure what's needed is a custom field that should be used as a document ID or maybe it's worth keeping the only allowed primary key field as Maybe there is a use case where this indeed makes sense to point collection to a custom id field instead of |
I don't have any strong preference, we could totally go the way elasticsearch handle the issue and have the Since we already have the option to set |
Now document collection works with an index field which has to be autogenerated.
In other workds, idFieldName has to always be autogenerated.
As an enhancement, we should support also custom fields to work as primary index.
The text was updated successfully, but these errors were encountered: