Version Information

Server Version: 2.1.1

Environment

OSS

What is the expected behaviour?

reload_metadata API calls should probably report that, although the operation was successful, inconsistencies are present.

What is the current behaviour?

I'm a little surprised to notice that reload_metadata just reports success even though the schema isn't consistent.

As it stands, I have to call reload_metadata and get_inconsistent_metadata sequentially to confirm whether or not the schema is consistent. Is this expected?

How to reproduce the issue?

1. Using replace_metadata with "allow_inconsistent_metadata": true, create inconsistencies (for example track a wrong table)
2. call reload_metadata: get a success
3. call get_inconsistent_metadata: get inconsistent_objects