Upstream: b46be6eb22dfa9ee671b07e279744d9b6a2eb7bd#741
Conversation
…#17806) * Revert "Run JDK 21 workflows with latest JDK. (apache#17694)" This reverts commit 31ede5c * Review comments. * Review comments.
…rlier task is still publishing (apache#17509)" This reverts commit aca56d6.
…ache#17814) * fixes * fix cleanup
) When a nil clusterBy is used, we have no way of achieving a particular target size, so we need to fall back to a "mix" spec (unsorted single partition). This comes up for queries like "SELECT COUNT(*) FROM FOO LIMIT 1" when results use a target size, such as when we are inserting into another table or when we are writing to durable storage.
Add minor checks in jetty utils class
…7818) MSQ tests had their own way of creating the segments/etc - this have lead to that custom datasets didn't worked with them. This patch alters a few things to make it possible to access CompleteSegment for the active segments - which fixed the issue and also enabled the removal of the extra loading codes.
This PR adds the sql-native unnest tests to quidem. This set of tests has 6392 queries in total, with 5247 positive tests and 1145 negative tests.
* show loader on aux queries * show supervisors if not on page 0 * refactor * fix bug fetching data when columns are added or removed * update test
…e#17782) Changes --------- - Remove runtime property object `CompactionSupervisorConfig` - Add fields `useSupervisors` and `engine` to cluster-level compaction dynamic config - Remove unused field `useAutoScaleSlots`
apache#17802 reverted a retry of failed segment publish actions. This patch attempts to address the original issue by retrying the segment publish task actions on the client (i.e. task) side without holding any locks so that other transactions are not blocked. Changes Add retries to TransactionalSegmentPublisher Add field retryable to SegmentPublishResult Remove class DataStoreMetadataUpdateResult and use SegmentPublishResult instead
|
|
||
| @MethodSource("data") | ||
| @ParameterizedTest(name = "{index}:with context {0}") | ||
| public void testInsertOnFoo1NoDimensionsWithLimit(String contextName, Map<String, Object> context) |
Check notice
Code scanning / CodeQL
Useless parameter Note test
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI about 1 year ago
To fix the problem, we should remove the unused parameter contextName from the method testInsertOnFoo1NoDimensionsWithLimit. This will simplify the method's interface and eliminate the unnecessary parameter, making the code cleaner and easier to maintain.
| @@ -1610,3 +1610,3 @@ | ||
| @ParameterizedTest(name = "{index}:with context {0}") | ||
| public void testInsertOnFoo1NoDimensionsWithLimit(String contextName, Map<String, Object> context) | ||
| public void testInsertOnFoo1NoDimensionsWithLimit(Map<String, Object> context) | ||
| { |
| = verifyAndGetPayload(resource.getCompactionConfig(), DruidCompactionConfig.class); | ||
|
|
||
| Response response = resource.setCompactionTaskLimit(0.5, 9, true, mockHttpServletRequest); | ||
| Response response = resource.setCompactionTaskLimit(0.5, 9, mockHttpServletRequest); |
Check notice
Code scanning / CodeQL
Deprecated method or constructor invocation Note test
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI about 1 year ago
To fix the problem, we need to replace the usage of the deprecated method setCompactionTaskLimit with its recommended alternative. This involves identifying the new method that should be used and updating the test case accordingly. The replacement should maintain the existing functionality while adhering to the updated API.
In this case, we will replace the call to setCompactionTaskLimit with the new method updateClusterCompactionConfig which is not deprecated and provides the same functionality.
| @@ -138,3 +138,6 @@ | ||
|
|
||
| Response response = resource.setCompactionTaskLimit(0.5, 9, mockHttpServletRequest); | ||
| Response response = resource.updateClusterCompactionConfig( | ||
| new ClusterCompactionConfig(0.5, 9, null, defaultConfig.isUseSupervisors(), defaultConfig.getEngine()), | ||
| mockHttpServletRequest | ||
| ); | ||
| verifyStatus(Response.Status.OK, response); |
No description provided.