Howdy, How difficult would it be for a Calcite user to add their own type to the type system? Is there a define process for doing this?
In our system, a relationship is a semantic type which is physically a long integer. We’ve been able to get by with typing relaltionship fields as SqlTypeName.BIGINT, but it requires a lot of gymnastics, including our own type analysis, inference, and propagation systems. Recently we’ve hit an issue which would require some substantial changes to this extra type system, which exists solely to compensate for the lack of this specific type in Calcite. For us, the ideal solution is to add this type, which would be *an* integer type, in Calcite, and let the Calcite type system handle everything. Is this feasible? Thanks! -Ian J. Bertolacci
