-
Notifications
You must be signed in to change notification settings - Fork 105
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
Vorto Repository startup fails #2180
Comments
After the technical user field has been created, existing data in the DB has to be migrated. For that we will need a script that adds the field. |
Looks like this is not only about the field itself but it also seems to need a value. Working on something - see also #2159 |
I have a branch here, containing a quick SQL script that should take care of fixing local user tables. |
I have updated the migration script after a chat with Alex, but due to the lack of clarity on certain DB fields (e.g. why do we have both an AUTHENTICATION_PROVIDER and an AUTHENTICATION_PROVIDER_ID fields?), I would rather test the script first on the development environment. |
Need to fix the script again after looking at dev environment: for instance bosch ids do not seem to have fixed length as I first thought. |
New update to the script as a procedure this time, as the @aedelmann PR here. |
After I have pulled to the latest commit, the repository startup is failing with an exception. The same problem exists on the vorto-dev system.
This is the exception:
2019-12-13 15:40:10.547 ERROR 16983 --- [main] o.s.boot.SpringApplication : Application startup failed
org.springframework.orm.jpa.JpaSystemException: Null value was assigned to a property [class org.eclipse.vorto.repository.domain.User.isTechnicalUser] of primitive type setter of org.eclipse.vorto.repository.domain.User.isTechnicalUser; nested exception is org.hibernate.PropertyAccessException: Null value was assigned to a property [class org.eclipse.vorto.repository.domain.User.isTechnicalUser] of primitive type setter of org.eclipse.vorto.repository.domain.User.isTechnicalUser
at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:333) ~[spring-orm-4.3.17.RELEASE.jar!/:4.3.17.RELEASE]
at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:244) ~[spring-orm-4.3.17.RELEASE.jar!/:4.3.17.RELEASE]
...
The text was updated successfully, but these errors were encountered: