Skip to content

Breaking change: dates and columnar load
Compare
Choose a tag to compare
@randyzwitch randyzwitch released this 22 Apr 18:25
· 69 commits to master since this release
v0.11.0
268acf8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

In this release, a breaking change was made related to how OmniSci version 4.6+ handle dates on the backend. The new behavior is related to storing dates as epoch days instead of seconds. This means the following:

  • for MapD/OmniSci <= 4.6, YOU MUST USE pymapd < 0.11 (a RuntimeError is thrown if version < 4.6 detected)
  • For OmniSci 4.6+, pymapd >= 0.11 is required. No error message will be thrown if using previously released versions of pymapd (i.e. these versions are in the wild, no way to change previously downloaded versions)

Additionally, python 3.5 was dropped, as f-strings are now used within pymapd (a 3.6+ feature). pyarrow 0.13 is also now supported.

Notable PRs:

Update build files for pyarrow 0.13 (#195)
Remove python 3.5 compat (#207)
Swap itertuples for .values (#210)
Make DATEs consistent with respect to changes in Omnisci Core (#188)
Throw exception if version number <4.6 (#220)

Assets 2
Loading