-
Notifications
You must be signed in to change notification settings - Fork 648
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
timestamps in get_relative_account_history() call #487
Comments
Hi there, you need to use the new elasticsearch plugin to make this, documentation is in progress but you can get some of it at: https://github.com/oxarbitrage/worker-proposals/blob/master/elasticsearch-plugin.md - #358 For example, getting the last op from the network will return:
The If you need help, have questions, etc please post here or open new issues accordingly. |
There is no infrastructure of ES yet. Can we not simply add the blocks timestamp to the APIs output? |
i don't think so. first there are performance issues to fetch the block and later the timestamp with each op, no code to do it was accepted. second, the output of the api call is just ops, if we add the timestamp we will be changing the format of the output possible breaking ongoing applications. we can go over this by adding a new api call but (third), we developed the ES plugin just for that (between other reasons), to don't add more stuff the the current api outputs, now is timestamp, then is filter by op, then filter by transaction, and so on. the ES is a global solution for this kind of situations of all kind of searches inside account history. I agree there is no infrastructure but all you need is to setup your own node with |
we need to educate IMHO to start resolving this issues by the plugin where everything can be done instead of just adding more stuff to the account history api outputs and more api calls. |
Done via #2642 |
Is it possible to get the timestamp for every operation in the account history?
The text was updated successfully, but these errors were encountered: