innobi
feature/choose-hyper-version
@davidsonhr1 Have you checked what happens if a version 2 writer attempts to write to an existing version 0 or version 1 hyper file?
@davidsonhr1 Have you checked if a version 2 writer attempts to write to an existing version 0 or version 1 hyper file?
So far I have only tested with files that I use in my company and they are version 2, I have only tested the scenario of a 100% new file, but I can test other scenarios
How old is the version 2? I very loosely only have pantab supporting technologies that are 1.5 to 2 years max. If version 2 has been out that long, I would also be fine to make that the default value.
Of course still want to know a little bit more about what @jorwoods is asking - I would hate to change that value and break things for users that are appending to Hyper databases created with prior verions of pantab
If it's fully backwards compatible, then defaulting to version 2 might be preferable.
FWIW the newer releases of the Hyper API have forced us to upgrade to version 4 for single point precision support (see https://github.com/innobi/pantab/pull/313) so your more immediate need may be solved, but I still think this PR to help with general option setting would be a great addition!
As it turns out, hyper versions are not backwards compatible. The most recent pantab version bumped to hyper version for to support numeric data and I think arm chips on Mac, but that has caused issues for tools that read older versions.
We probably need to keep the default version at 0 and warn when updating in the future? I'll see if Tableau can provide more clarity on this field as well
Thanks for the PR! This has been superseded by https://github.com/innobi/pantab/pull/335 though