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
persistence_idGenerationMode_<ENTITY> is not applied #1737
Comments
That's odd |
Sure:
This is the full log: |
Thanks for the log. Unfortunately, in it, FROST is not fully initalised yet. It doesn't fully initialise the data model until the first request to an entity type is done... |
I found out the issue and it is caused by a small inconsistency: This is an inconsistency because a setting like plugins_coreModel_idType_thing=STRING works. I hope this can help! |
Indeed, that case different is confusing. |
According to the documentation, it is possible to override the default persistence.idGenerationMode:
**persistence.idGenerationMode.:** Since 2.2.0 Determines how entity ids are generated for this Entity Type. This overrides **persistence.idGenerationMode**.
Current Behavior:
If I try to set persistence_idGenerationMode_thing for example, the ovveride is not applied (it tried Thing capital case too).
During the startup in the startup log, the setting is not mentioned and appears to be ignored.
Expected Behavior:
If I use the environmental variables:
persistence_idGenerationMode is set to
ServerGeneratedOnly
persistence_idGenerationMode_thing is set to
ServerAndClientGenerated
Then:
The it is possible to create Things of the assigned id.
Logs:
Environment
Application Version:
fraunhoferiosb/frost-server-http:latest
The text was updated successfully, but these errors were encountered: