public final class ConnectorCatalog extends Object
EDbVendor, and describes the navigation hierarchy each connector
exposes (Database / Schema / Table, Project / Dataset / Table, etc.).
This catalog is the single source of truth for "which SQL dialect does this M step belong to?" Every new connector we support must be registered here, ideally with a quick corpus sample that demonstrates real-world use.
Aliases are intentionally case-insensitive because M is itself case-sensitive for identifier lookup, but different corpus sources occasionally normalize casing.
| Modifier and Type | Method and Description |
|---|---|
static List<String> |
expectedHierarchy(EDbVendor vendor)
Canonical navigation-segment hierarchy for a given vendor.
|
static boolean |
isKnownConnector(String qualifiedFunctionName) |
static EDbVendor |
vendorFor(String qualifiedFunctionName)
Look up the vendor for a qualified function name such as
"Snowflake.Databases". |
public static EDbVendor vendorFor(String qualifiedFunctionName)
"Snowflake.Databases". Returns null when the
connector is unknown — callers must decide whether to fall back to
a user-supplied --inner-vendor override or skip the step.public static List<String> expectedHierarchy(EDbVendor vendor)
source{[Name=…,Kind=…]}[Data] chain's shape and
to drive synthetic SQL construction in
TPowerQueryAnalyzer.public static boolean isKnownConnector(String qualifiedFunctionName)