We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've noticed that queries involving blocks 386620 and 392110 and erc20 fail. I have no idea.
Here are example queries
select * from ethereum.default.erc20 where erc20_blocknumber = 392110;
I do not believe that there are any erc20 token transactions in those blocks but I don't think that they should be resulting in an error either.
Ethereum node is parity 1.10.4
respose example from presto
presto> select * from ethereum.default.erc20 where erc20_blocknumber = 392110;
Query 20180807_224852_00845_hwt4f, FAILED, 1 node Splits: 17 total, 0 done (0.00%) 0:00 [0 rows, 0B] [0 rows/s, 0B/s]
Query 20180807_224852_00845_hwt4f failed: Index: 0, Size: 0
The text was updated successfully, but these errors were encountered:
same issue with block 505500
Sorry, something went wrong.
These same blocks fail when the ethereum node is infura as well.
No branches or pull requests
I've noticed that queries involving blocks 386620 and 392110 and erc20 fail. I have no idea.
Here are example queries
select * from ethereum.default.erc20 where erc20_blocknumber = 392110;
select * from ethereum.default.erc20 where erc20_blocknumber = 392110;
I do not believe that there are any erc20 token transactions in those blocks but I don't think that they should be resulting in an error either.
Ethereum node is parity 1.10.4
respose example from presto
presto> select * from ethereum.default.erc20 where erc20_blocknumber = 392110;
Query 20180807_224852_00845_hwt4f, FAILED, 1 node
Splits: 17 total, 0 done (0.00%)
0:00 [0 rows, 0B] [0 rows/s, 0B/s]
Query 20180807_224852_00845_hwt4f failed: Index: 0, Size: 0
The text was updated successfully, but these errors were encountered: