Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-25250

Fixing hacky test in TestCoprocessorInterface

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.3.2
    • None
    • None
    • None

    Description

      The coprocessor was not being initialized in the region/store as the regionServices was set as null. The test was using an explicit setter in the region for populating the coprocessor after region initialization. This code path was exercised only by tests. This commit removes the back door entry for the test to set the coprocessor host explicitly and now the same is being set through the regular store initialization code path. This also allows the use of the storecontext otherwise the test would fail with the storecontext having a null coprocessor

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            abhishekkhanna.01 Abhishek Khanna

            Dates

              Created:
              Updated:

              Slack

                Issue deployment