Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Darwin 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64Python 3.4.5 :: Anaconda custom (x86_64)64conda also tried pip)
Now that you know a little about me, let me tell you about the issue I am
having:
# Description of Issue
* Tried to ingest quantopian-quandl dataset, and run the starting out buy_appl.py algo but it failed...
* `$ zipline ingest -b quantopian-quandl` results in `assets-5.sqlite` being populated in `~/.zipline/data/quantopian-quandl/2016-08-29T15;57;26.244897` but not `assets-3.sqlite`
* Result of running `$ zipline run -b quantopian-quandl --algofile ./buyapple.py --start 2010-1-1 --end 2014-1-1 -o buyapple_out.pickle` - `sqlalchemy.exc.InvalidRequestError: Could not reflect: requested table(s) not available in sqlite:////Users/yixin/.zipline/data/quantopian-quandl/2016-08-29T15;57;26.244897/assets-3.sqlite: (version_info, equities, futures_root_symbols, futures_contracts, futures_exchanges, asset_router)`
* Replacing `assets-3.sqlite` with content from `assets-5.sqlite` does not work as it spits out version difference error...
* To note - I ingested yahoo and quandl data, it works fine. This only applies to quantopian-quandl
Here is how you can reproduce this issue on your machine:
## Reproduction Steps
1. `$ zipline ingest quantopian-quandl`
2. `$ zipline run -b quantopian-quandl --algofile ./buyapple.py --start 2010-1-1 --end 2014-1-1 -o buyapple_out.pickle`
3. `sqlalchemy.exc.InvalidRequestError: Could not reflect: requested table(s) not available in sqlite:////Users/yixin/.zipline/data/quantopian-quandl/2016-08-29T15;57;26.244897/assets-3.sqlite: (version_info, equities, futures_root_symbols, futures_contracts, futures_exchanges, asset_router)`
...
## What steps have you taken to resolve this already?
Instead of using quantopian-quandl I used yahoo and quandl data, works fine. But I still want to resolve this issue because it blocks lot of people who want to peek into zipline but can't due to outdated documentation...
...
# Anything else?
No, but thank you guys for looking into it. Great work!
...
Sincerely,
Yixin Xia
Thanks @wongasta . We unintentionally started pushing a more recent version. Fixing it now...
Thanks man! Appreciate all the great work!!!
Should be fixed now. Does a new ingest work for you?
zipline 1.0.2 should fix this now. Definitely re-open if that's not the case.
@richafrank I'm running into a similar issue, although with zipline 1.0.2. I just installed it (conda) and ran zipline ingest.
sqlalchemy.exc.InvalidRequestError: Could not reflect: requested table(s) not available in sqlite:////Users/paul/.zipline/data/quantopian-quandl/2016-12-18T15;39;05.317714/assets-5.sqlite: (asset_router, futures_root_symbols, version_info, equity_symbol_mappings, equities, futures_contracts, futures_exchanges)
Here's the content of my ~/.zipline/data/quantopian-quandl/2016-12-18T15\;47\;58.666481/ data dir:
adjustments.sqlite
assets-3.sqlite
assets-6.sqlite
daily_equities.bcolz
minute_equities.bcolz
It looks like assets-5.sqlite wasn't ingested or ASSET_DB_VERSION isn't set correctly (?).
Thanks!
Ah thanks - I'll bump the published bundle to include assets-5...
FWIW We want to remove these manual steps but haven't gotten to it.
any update on fixing sqlalchemy.exc.InvalidRequestError?
sqlalchemy.exc.InvalidRequestError: Could not reflect: requested table(s) not available in Engine(sqlite:////home/wenchen/.zipline/data/quantopian-quandl/2017-02-28T19;35;45.731723/assets-6.sqlite): (equity_supplementary_mappings, futures_root_symbols, version_info, equity_symbol_mappings, equities, futures_contracts, futures_exchanges, asset_router)
I'm running the buyapple example and after the suggestion from https://github.com/quantopian/zipline/issues/1316, I still got the same error on ubuntu 16.04.
zipline was install initially with pip but later from sudo -H pip install -e git+https://github.com/quantopian/zipline@master#egg=zipline_master
do removed ~/.zipline but still the same issue.
Please help,
Thanks
Most helpful comment
Thanks @wongasta . We unintentionally started pushing a more recent version. Fixing it now...