Skip to content

Conversation

dmitry-timofeev
Copy link
Contributor

Overview

Add BlockchainData#createIndexProof.


See: https://jira.bf.local/browse/ECR-4176

Definition of Done

  • There are no TODOs left in the code
  • Change is covered by automated tests
  • The coding guidelines are followed
  • Public API has Javadoc
  • Method preconditions are checked and documented in the Javadoc of the method
  • Changelog is updated if needed (in case of notable or breaking changes)
  • The continuous integration build passes

Fork fork = db.createFork(cl);

// Use the full index name
String fullIndexName = serviceName + "." + simpleIndexName;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found that this code is frequently used. Maybe it's time to consider creating a function somewhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In tests I think it's OK to use it, but where else? The service schemas has been migrated to simple names (they no longer need explicit namespacing since #1393 ).

It might make sense to make it public in the BlockchainData if it is needed in proof creation (but I am not sure it will be needed).

@dmitry-timofeev dmitry-timofeev changed the base branch from replace-ro-fork-with-erased-ECR-4176 to numeric-index-ids-for-cache February 4, 2020 13:33
@dmitry-timofeev dmitry-timofeev force-pushed the add-index-proof-to-bd-ECR-4176 branch from cb1e35b to 9911b3d Compare February 4, 2020 13:34
@dmitry-timofeev
Copy link
Contributor Author

Rebased onto target

@dmitry-timofeev dmitry-timofeev merged commit 656b9a6 into numeric-index-ids-for-cache Feb 4, 2020
@dmitry-timofeev dmitry-timofeev deleted the add-index-proof-to-bd-ECR-4176 branch February 4, 2020 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants