Filter transactions from get_account_history result based on block number about bitshares-core HOT 3 CLOSED

From @theoreticalbts on August 18, 2015 16:7

Allowing negative block numbers for relative to head is a bad idea -- the client will likely want to track block numbers on its own.

We need a new index of (account ID, block number) -> operation_history_id where the ohid is the last op by the account in the block. The index should be disabled unless requested on the CLI. Disabling will increase performance but get_account_confirmed_history() will not be able to query based on block number.

from bitshares-core.

Can be done easy with the new elastic search plugin.

search in a block range:

curl -X GET 'http://localhost:9200/graphene-*/data/_search?pretty=true' -d '
{
    "query" : {
        "bool" : { "must" : [{"term": { "account_history.account.keyword": "1.2.24484"}},{"term": { "operation_type": 0}}, {"range": {"block_data.block_num": {"gte": 20822908, "lte": 21822908}}}] }
    }
}
'

count:

curl -X GET 'http://localhost:9200/graphene-*/data/_count?pretty=true' -d '
{
    "query" : {
        "bool" : { "must" : [{"term": { "account_history.account.keyword": "1.2.24484"}},{"term": { "operation_type": 0}}, {"range": {"block_data.block_num": {"gte": 20822908, "lte": 21822908}}}] }
    }
}
'

from bitshares-core.

closing this one as it can be done by using the commands above in a node with ES plugin. full documentation at https://github.com/bitshares/bitshares-core/wiki/ElasticSearch-Plugin

from bitshares-core.