Skip to content
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

es-objects plugin does not load genesis data. #1652

Zapata opened this issue Mar 14, 2019 · 2 comments


3 participants
Copy link

commented Mar 14, 2019

Bug Description
es-objects plugin does not load genesys data.

As an example users that are in the genesis file and didn't update their account are not found in the populated objects-account index.
This may be true for other types of data.

Genesis data is needed in order to have a consistent and complete data in ES.

Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.

  • API (the application programming interface)
  • Build (the build process or something prior to compiled code)
  • CLI (the command line wallet)
  • Deployment (the deployment process after building such as Docker, Travis, etc.)
  • DEX (the Decentralized EXchange, market engine, etc.)
  • P2P (the peer-to-peer network for transaction/block propagation)
  • Performance (system or user efficiency, etc.)
  • Protocol (the blockchain logic, consensus, validation, etc.)
  • Security (the security of system or user data, etc.)
  • UX (the User Experience)
  • Other (please add below)
    • Elastic Search Plugin

Steps To Reproduce

  1. Populate an ElasticSearch using the ES plugin.
  2. Search for genesys users:
GET /objects-account/_search
  "query": {
    "terms": {
      "object_id": [

Expected Behavior
The accounts should be available in objects-account ES index.

Host Environment


  • Evaluate / Prioritize Bug Report
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation

@oxarbitrage oxarbitrage added this to To do in Feature Release (3.1.0) via automation Apr 2, 2019

@oxarbitrage oxarbitrage added this to the 3.1.0 - Feature Release milestone Apr 2, 2019

@oxarbitrage oxarbitrage self-assigned this Apr 2, 2019

@abitmore abitmore moved this from To do to In development in Feature Release (3.1.0) Apr 12, 2019


This comment has been minimized.

Copy link

commented Apr 23, 2019

closed by #1717

Feature Release (3.1.0) automation moved this from In development to Done Apr 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.