Metastore Location Confusion

A recurring configuration/usage mismatch where specifying a bucket or path where a registered table name is expected leads to parse/semantic errors, requiring the system’s location-aware API (e.g., a location() resolver) instead of raw paths.