araddon/qlbridge

Function Registries, and enforce function existence errors

araddon opened this issue · 0 comments

Currently the function-registry is assumed to be global scope. This is flawed, each table in a schema would have its own function registry, so that a elasticsearch backed table would not have the same available functions as say a mysql one, etc.