Hey everyone, I'm curious if anyone knows the reason behind choosing 38 as a MAX_PRECISION for DecimalType in the Table API?
I needed to process decimal types larger than that and I ended up monkey-patching DecimalType to use a higher precision. I understand it adds a bit of overhead, but I haven't noticed any serious problems. Maybe this number can be configured. I noticed it's hardcoded in a few places, but it should be a fairly straightforward change. Thanks!
