code.onehippo.org is currently readonly. We are migrating to code.bloomreach.com, please continue working there on Monday 14/12. See: https://docs.bloomreach.com/display/engineering/GitLab

  • Ard Schrijvers's avatar
    REPO-1942 [Backport 4.2.7] Fix hippo lock table creation for MySQL · 9cf8a21f
    Ard Schrijvers authored
    Make sure that *if* the Hippo lock table exists, that it really contains
    an index on lockKey (regardless whether it is a primary key or a unique
    index). If it doesn't contain one, the lock table was not created
    correctly and contains locks that do not work. Hence, truncating the
    lock table is ok. After that, correct the table scheme. Right after
    the table scheme has been fixed, other running cluster nodes can log
    some errors wrt locks. This is not a problem and expected
    
    (cherry picked from commit 90938409)
    9cf8a21f
Name
Last commit
Last update
api Loading commit data...
builtin Loading commit data...
config Loading commit data...
connector Loading commit data...
dependencies Loading commit data...
deprecated Loading commit data...
engine Loading commit data...
jaxrs Loading commit data...
mockutils Loading commit data...
modules Loading commit data...
provider Loading commit data...
resources Loading commit data...
scripts Loading commit data...
servlets Loading commit data...
test Loading commit data...
testcontent Loading commit data...
testutils Loading commit data...
upgrade Loading commit data...
utilities Loading commit data...
workflow Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
LICENSE Loading commit data...
NOTICE Loading commit data...
README Loading commit data...
pom.xml Loading commit data...