Open phelps-sg opened 10 months ago
Hi, By design zipline has put constraints on how the data is stored. Unfortunately, one would have to do the changes in the code. I am working on switching to parquet and relax some constraints, but I haven't had much time to finalize this.
Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment
Now that you know a little about me, let me tell you about the issue I am having:
Description of Issue
When ingesting data for crypto pairs we often encounter large volumes which cannot be represented in uint32.
Here is how you can reproduce this issue on your machine:
Reproduction Steps
What steps have you taken to resolve this already?
...
Anything else?
Can we use 64-bit int for representing volumes to support crypto? ...
Sincerely, Steve Phelps