I think that there may be two related problems: too many instructions and too often executed.
When I run your query in the console [YQL] [yql], I see the answer partially:
<javascript execution-time="6783" instructions-used="50024350" table-name="yahoo.finance.historicaldata"/> <javascript name="yahoo.finance.historicaldata" verb="select"> <![CDATA[java.lang.RuntimeException: Too many instructions executed: 50024350]]> </javascript>
You can see that the problem is "too many instructions completed."
Looking at the query example for this table, it looks like the start and end dates for this table use the format yyyy-mm-dd. Thus, your request can be rewritten as:
select * from yahoo.finance.historicaldata where symbol = "TW.L" and startDate = "2011-01-01" and endDate = "2011-01-22"
This updated query worked for me a couple of times, but now I get an additional error on the locked table:
<javascript name="yahoo.finance.historicaldata" verb="select"> <![CDATA[com.yahoo.platforms.pipes.model.ModuleException: Error Codes: js.blocked.execute.request Message: "The current table 'yahoo.finance.historicaldata' has been blocked. It exceeded the allotted quotas of either time or instructions"]]> </javascript>
It is possible that one leads to another; in other words, a garbled query causes so many commands to run that it causes the table to lock.
source share