Is there a mechanism for conveying the max-digits of a field in tap schemas? (e.g. tap-mysql). I fixed target-bigquery to differentiate DECIMAL from FLOAT: https://github.com/adswerve/target-bigquery/issues/22 But if a MySQL column is defined thusly: ``amount` numeric(65, 2) NOT NULL` then I need a BIGDECIMAL not a DECIMAL in the target. I don’t see a way to convey the max digits in JSONSchema. (Short of a “max/min” field, but JSON doesn’t have enough digits to hold the actual max). So that

65

is currently omitted from the tap’s singer schema as far as I can see:

"amount": {
            "inclusion": "available",
            "multipleOf": 0.01,
            "type": [
              "null",
              "number"
            ]
          },

One other solution is just to flag “use BIGDECIMAL instead of DECIMAL” for all columns created in BQ by the target. But that’s obviously not a universal solution.