Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-19026

Do not drop CQLTester.KEYSPACE content in @After asynchronously

    XMLWordPrintableJSON

Details

    • Task
    • Status: In Progress
    • Normal
    • Resolution: Unresolved
    • 4.0.x, 4.1.x, 5.0.x, 5.x
    • Test/unit
    • None
    • Semantic
    • Low Hanging Fruit
    • All
    • None
    • Hide

      run jvm tests

      Show
      run jvm tests

    Description

      CASSANDRA-18710 showed that removal of tables, views, functions, etc. in @After method asynchronously may span the next test case and modify that test behaviour in some unexpected way

      Concretely, @After method includes dropping KEYSPACE_PER_TEST synchronously and the whole content of KEYSPACE asynchronously. I don't see a reason for dropping the content of KEYSPACE after each test because that keyspace is not expected to be clean for each test case. It is the case for KEYSPACE_PER_TEST. Therefore I propose removal of that async cleanup of KEYSPACE after each test case.

      Attachments

        Issue Links

          Activity

            People

              jlewandowski Jacek Lewandowski
              jlewandowski Jacek Lewandowski
              Jacek Lewandowski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: