Integers should be interpreted as unix timestamps

[kerinin]

Per Wikipedia:

Unix time[a] is a date and time representation widely used in computing. It measures time by the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, the beginning of the Unix epoch, without adjustments made due to leap seconds.[3]

Currently, if you load a CSV containing integers they appear to be interpreted as nanosecon-precision unix timestamps, which isn't a very common interpretation of integers in the data-processing community.

In this same vein, if you load a CSV containing numbers with decimals, they fail to convert to timestamps - we should support interpreting floating point values as unix timestamps as well.

[bjchambers]

At least some of this is Arrow default behavior. Are you referring to "in the time column" or in general? I would have expected a general column containing integers to be treated as a numeric column, and not convert to nanosecond timestamps or second precision timestamps.