Open lminer opened 4 months ago
@lminer there are 2 ways you can solve your issue:
Thanks for the suggestions. I did not know about the optional inputs! Unfortunately, both of those solutions add a lot more complexity that is difficult to manage and would be bug prone, at least in our context. We'll probably just opt to add more model names. I just want to reiterate that I think this feature request would be a nice longterm solution. Input and output shapes inevitably change as models evolve, and this would allow for easier swapping between different versions, without having to define dozens of version specific inputs and outputs in the config.pbtxt.
We would like to be able to deploy multiple versions of the same model. Unfortunately, they will not necessarily always have the same shapes and dtypes.
It would be great to have a per version config.pbtxt (maybe nested in the version directory itself).
Another option would be to simply have different model names for these versions, but that doesn't seem as clean as they are so tightly related and it would lead to a proliferation of names.