[FEA] Save input and output schema when `.save` methods are called on models

[oliverholworthy]

Relates to: https://github.com/NVIDIA-Merlin/Merlin/issues/545

🚀 Feature request

Provide a consistent .save interface for all models.

This .save method should save the model artifact along with the schema to a directory provided.

Motivation

Model artifacts alone are not enough to unambiguously infer the correct input schema for a model. Saving the input schema along with models will enable serving code in systems to figure out the correct inputs required for models from an artifact without requiring the user to provide the schema at serving time.

Part of: https://github.com/NVIDIA-Merlin/Merlin/issues/489

Proposed interface

Create a runtime check-able protocol that specifies the common methods expected on a model object.

This .save method on a model will write out the model artifact(s) along with the input schema to a directory provided.

Files saved in merlin metadata directory.

• input_schema.json and output_schema.json). Serialized Merlin Schema using the TensorflowMetadata format currently provided in merlin.core
• model.json
  • module and class names to support reconstructing the same model

Saved model directory structure

• model artifacts to be saved in top-level of directory
• merlin metadata to be saved in merlin_metadata subdirectory.

e.g. a model.save("my_merln_model") on a tensorflow backend should result in the following directory structure:

my_merlin_model
├── merlin_metadata
│   ├── input_schema.json
│   ├── output_schema.json
│   └── model.json
├── assets
├── keras_metadata.pb
├── saved_model.pb
└── variables
    ├── variables.data-00000-of-00001
    └── variables.index

Sub-Tasks

• #677
• #676

[EvenOldridge]

@marcromeyn @oliverholworthy what's the status of this? This is blocking the creation of example notebooks for end to end using systems.

[rnyak]

partially addressed by https://github.com/NVIDIA-Merlin/models/pull/680

[oliverholworthy]

This PR (https://github.com/NVIDIA-Merlin/models/pull/680) handles the first two tasks.

• Adding the protocol
• and updating save method of tensorflow models.

There is a bit more to think about beyond this. Adding output schema for tensorflow models. And figuring out how to enforce that a schema is created. Since the Merlin Models API is flexible enough at the moment that we can't always guarantee that we have a schema available. At least not in a way that provides any more information than the saved model signature is able to (since we could infer the schema from the saved model like we do in Merlin Systems currently).