DateColumn incorrectly recognized as StringColumn in Tablesaw v0.43.1

[samarthsharmaLTC]

While validating a CSV file using Tablesaw version 0.43.1, I encountered a type casting issue: columns intended as DateColumn were automatically detected as StringColumn. This led to downstream type mismatch errors during validation. The source CSV contains date values in standard ISO format, and the schema was defined to expect DateColumn. Requesting guidance on whether this is a parsing limitation, a configuration oversight, or a bug in the column inference logic.

[lwhite1]

try (1) checking to see if all your dates are actually using the same format and (2) adding a special format that matches what you have.

…

On Tue, Jul 8, 2025 at 6:40 AM samarthsharmaLTC ***@***.***> wrote: *samarthsharmaLTC* created an issue (jtablesaw/tablesaw#1301) <#1301> While validating a CSV file using Tablesaw version 0.43.1, I encountered a type casting issue: columns intended as DateColumn were automatically detected as StringColumn. This led to downstream type mismatch errors during validation. The source CSV contains date values in standard ISO format, and the schema was defined to expect DateColumn. Requesting guidance on whether this is a parsing limitation, a configuration oversight, or a bug in the column inference logic. — Reply to this email directly, view it on GitHub <#1301>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2FPAUWCF37H64SZBUQSVL3HON3FAVCNFSM6AAAAACBAY3HEGVHI2DSMVQWIX3LMV43ASLTON2WKOZTGIYTCOJZGYZTGNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>