MUPIP LOAD option to ignore mode of MUPIP EXTRACT that created ZWR extract
Final Release Note
The -ignorechset
command line option of MUPIP LOAD tells MUPIP to load the extract even if it was created by a MUPIP process in another mode (UTF-8 mode vs. M mode). As using -ignorechset
bypasses YottaDB checks, use it only if you are sure that the extract file can be loaded correctly. Since the mode only applies to textual representation of the data, and the underlying binary format is the same, BINARY format extracts ignore the mode of the extract.[#569 (closed)]
Description
Avoid errors such as this where loading the mode-independent PostgreSQL seed for Octo in UTF-8 mode fails because the seed was created in M mode. The seed appears to have only characters in the 0…127 ASCII range, and hence is correct in both M and UTF-8 modes.
$ echo $ydb_chset
UTF-8
$ mupip load $ydb_dist/plugin/octo/postgres-seed.zwr
GT.M MUPIP EXTRACT
01-JUL-2019 00:29:12 ZWR
%YDB-E-LOADINVCHSET, Extract file CHSET (M) is incompatible with ydb_chset/gtm_chset
%YDB-E-MUNOFINISH, MUPIP unable to finish all requested actions
$
Draft Release Note
The -ignorechset
command line option of MUPIP LOAD tells MUPIP to load the extract even if it was created by a MUPIP process in another mode (e.g., UTF-8 mode vs. M mode). Previously, for any YottaDB post #493 (closed) this would fail with a LOADINVCHSET error. The workaround was to edit the extract file with a text editor or to run MUPIP LOAD in the same mode as the MUPIP EXTRACT. As using -ignorechset
bypasses YottaDB checks, use it only if you are sure that the extract file can be loaded correctly. [#569 (closed)]