New issue
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
Cannot search tags within a range of blocks #2759
Comments
Do you index |
yes - index_all_tags is set |
melekes
added a commit
that referenced
this issue
Nov 22, 2018
previously, it was returning a height even for range conditions: "height < 10000". Refs #2759
melekes
added a commit
that referenced
this issue
Nov 22, 2018
previously, it was returning a height even for range conditions: "height < 10000". Refs #2759
melekes
added a commit
that referenced
this issue
Nov 22, 2018
Modify lookForHeight to return a height only there's a equal operator. Previously, it was returning a height even for range conditions: "height < 10000". Fixes #2759
ebuchman
pushed a commit
that referenced
this issue
Nov 27, 2018
Modify lookForHeight to return a height only there's a equal operator. Previously, it was returning a height even for range conditions: "height < 10000". Fixes #2759
Fixed on develop. Should be in v0.26.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tendermint version (use
tendermint version
orgit rev-parse --verify HEAD
if installed from source):0.25.0-0c9c3292
Environment: LotionJS
What happened:
Issuing a query with an inequality comparison for tx.height results in a string comparison. Specific example is the following query:
results in matches:
and the following query
returns an empty array []
What this means is that every attempt to query for tags within a range (which by definition includes a > and < operator) will return an empty array.
What you expected to happen:
tx.height should be compared as an integer so tags can be queried in a range of blocks. It appears that tx.height is stored as a string in the transaction which is perhaps the underlying problem:
The text was updated successfully, but these errors were encountered: