DDL based import statement incorrectly parses the foreign schema name

The DDL import statement like

IMPORT FOREIGN SCHEMA public FROM SERVER sampledb INTO accounts OPTIONS("importer.useFullSchemaName" 'false');

does not set the "importer.schemaPattern" to "public" instead it sets to "importer.schemaName" property to "public" in runtime thus invalidating its use.