MAPR HUE upgrade from 3.9 to 4.2 upgrade issues

#1

hue syncdb --noinput
Ran fine
Installing custom SQL …
Installing indexes …
Installed 0 object(s) from 0 fixture(s)

Synced:

django.contrib.auth
django_openid_auth
django.contrib.contenttypes
django.contrib.sessions
django.contrib.sites
django.contrib.staticfiles
django.contrib.admin
south
axes
about
filebrowser
help
jobbrowser
metastore
proxy
indexer
dashboard

Not synced (use migrations):

  • django_extensions
  • desktop
  • beeswax
  • hbase
  • jobsub
  • oozie
  • useradmin
  • notebook
    (use ./manage.py migrate to migrate these)

hue migrate --merge ( Ran with some issues)

Running migrations for desktop:

  • Migrating forwards to 0027_truncate_documents.

oozie:0001_initial
[03/Feb/2022 18:38:39 +0000] generic DEBUG execute “SET FOREIGN_KEY_CHECKS=0;” with params “[]”
[03/Feb/2022 18:38:39 +0000] generic DEBUG execute “SET FOREIGN_KEY_CHECKS=0;” with params “[]”
[03/Feb/2022 18:38:39 +0000] generic DEBUG execute “CREATE TABLE oozie_job (is_shared bool NOT NULL, description varchar(1024) NOT NULL, parameters longtext NOT NULL, deployment_dir varchar(1024) NOT NULL, schema_version varchar(128) NOT NULL, last_modified datetime NOT NULL, owner_id integer NOT NULL, id integer AUTO_INCREMENT NOT NULL PRIMARY KEY, name varchar(40) NOT NULL)” with params “[]”
FATAL ERROR - The following SQL query failed: CREATE TABLE oozie_job (is_shared bool NOT NULL, description varchar(1024) NOT NULL, parameters longtext NOT NULL, deployment_dir varchar(1024) NOT NULL, schema_version varchar(128) NOT NULL, last_modified datetime NOT NULL, owner_id integer NOT NULL, id integer AUTO_INCREMENT NOT NULL PRIMARY KEY, name varchar(40) NOT NULL)
The error was: (1050, “Table ‘oozie_job’ already exists”)
! Error found during real run of migration! Aborting.

! Since you have a database that does not support running
! schema-altering statements in transactions, we have had
! to leave it in an interim state between migrations.

! You might be able to recover with: = DROP TABLE oozie_job CASCADE; []
= DROP TABLE oozie_workflow CASCADE; []
= DROP TABLE oozie_link CASCADE; []
= DROP TABLE oozie_node CASCADE; []
= DROP TABLE oozie_mapreduce CASCADE; []
= DROP TABLE oozie_streaming CASCADE; []
= DROP TABLE oozie_java CASCADE; []
= DROP TABLE oozie_pig CASCADE; []
= DROP TABLE oozie_start CASCADE; []
= DROP TABLE oozie_end CASCADE; []
= DROP TABLE oozie_kill CASCADE; []
= DROP TABLE oozie_fork CASCADE; []
= DROP TABLE oozie_join CASCADE; []
= DROP TABLE oozie_coordinator CASCADE; []
= DROP TABLE oozie_dataset CASCADE; []
= DROP TABLE oozie_datainput CASCADE; []
= DROP TABLE oozie_dataoutput CASCADE; []
= DROP TABLE oozie_history CASCADE; []

! The South developers regret this has happened, and would
! like to gently persuade you to consider a slightly
! easier-to-deal-with DBMS (one that supports DDL transactions)
! NOTE: The error which caused the migration to fail is further up.
Error in migration: oozie:0001_initial
[03/Feb/2022 18:38:39 +0000] models INFO HuePermissions: 0 added, 0 updated, 23 up to date, 0 stale
Traceback (most recent call last):
File “/opt/mapr/hue/hue-4.2.0/build/env/bin/hue”, line 12, in
load_entry_point(‘desktop==4.2.0’, ‘console_scripts’, ‘hue’)()
File “/opt/mapr/hue/hue-4.2.0/desktop/core/src/desktop/manage_entry.py”, line 143, in entry

In the end, I ran this but it kind of faked changes
hue migrate --fake

How to undo fake changes and how do I successfully do schema changes ?