zabetak opened a new pull request, #6113:
URL: https://github.com/apache/hive/pull/6113

   ### What changes were proposed in this pull request?
   1. Add Derby support in QTestDatabaseHandler and implement proper setup and 
cleaup logic
   2. Refactor docker instructions in separate class and update class hierarchy
   3. Update all .q files using 'jdbc:derby' URLs to exploit the new 
functionality
   4. Re-enable previously disabled tests since flakiness is resolved.
   5. Rework dataconnector.q test exploiting the init script functionality and 
drop all Derby binary files.
   
   ### Why are the changes needed?
   1. Stabilize CI and avoid flakiness due to improper Derby init/cleanup
   2. Facilitate writing unit tests for Derby and improve their readability 
(e.g., `dataconnector.q`)
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   ### How was this patch tested?
   ```
   mvn clean test -Dtest=TestMiniLlapLocalCliDriver 
-Dqfile=authorization_privilege_objects.q,dataconnector.q,explain_jdbc.q,external_jdbc_auth.q,external_jdbc_join_mv.q,external_jdbc_rowcount.q,external_jdbc_table.q,external_jdbc_table3.q,external_jdbc_table4.q,external_jdbc_table_partition.q,external_jdbc_table_perf.q,external_jdbc_table_typeconversion.q,external_jdbc_view.q,jdbc_handler.q,jdbc_split_filter.q,qt_database_derby.q
 
   ```
   ```
   mvn test -Dtest=TestNegativeLlapLocalCliDriver.java 
-Dqfile=authorization_jdbc_keystore.q,dataconnector_authfail_alter.q,dataconnector_authfail_drop.q,dataconnector_authfail_remoteDB.q,external_jdbc_negative.q
   ```
   ```
   mvn clean test -Dtest=TestContribCliDriver -Dqfile=dboutput.q
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to