Jolan Rensen

https://bumptech.github.io/glide/doc/migrating.html There have been a lot of changes from v3 to v4, so if you can, please migrate it

Hmm, interesting thought, however, I'd say the current implementation is more in line with what is expected to happen. If we'd go by your approach `columnOf(1) == columnOf(listOf(1))`, which doesn't...

Agreed, similar to https://github.com/Kotlin/dataframe/issues/29 We'll definitely add KDocs before a 1.0 release.

okay, I looked over additionalProperties... https://swagger.io/docs/specification/data-models/dictionaries/ Let's see how I can add that

Hi! `java.math.BigDecimal` is supported at the moment, Since you want the type `Decimal`, does that suffice for you? Or should we add BigInteger too?

I see... So you actually would need a way to give the DataType in case it doesn't exist in or is different from the `knownDataTypes` in the Encoding.kt file... That's...

Hmm so whatever `DecimalType` I specify, it turns out that the dtype turns into `DecimalType(38,0)` anyways whenever I encode a `BigInteger`. So maybe I can just add a `BigInteger::class to...

> Just support for `BigInteger` would be perfect, and probably cover most use cases. `DecimalType.SYSTEM_DEFAULT()` is `Decimal(38, 18)` right, so something else would be needed for `Decimal(38, 0)`? Well yes,...

> > Interesting, this is what is used for `BigDecimal` already? I tried writing a data frame based on data classes with a `BigDecimal` field to a table with schema...

I'm afraid I don't know enough about this specific part of Spark to give a helpful answer. Maybe you should try StackOverflow for that too :)