-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[WIP] Tests for debugging Dart and MSQ in Quidem #17861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Add 2 tests for debugging Dart and Msq in Quidem.
downloaded the heapdump - the issue was caused by huge exceptions 5M each - and surefire tried to hold all of them in a map....which have lead to an OOM the underlying exception is a diff related exception; but it contains the following exception(s):
|
running the same query which errors out multiple times leads to the same issue: tt.iq
edit: copied the wrong testfile first time...this above should be the right one |
furthermore: forgot to mention that the same issue didn't appeared in my IDE - only from a maven run...which is also odd and even connecting with a remote debugger ( |
This PR splits up the iq files into smaller files at the testcase level. The files are grouped in subdirectories at the testsuite level. This version also makes the tests run for all 3 engines. The file name of an iq file indicicates what engine(s) the test uses: If all 3 engines expect the same results: *.all.iq: AllDruidEnginesComponentSupplier If one of the enigines expect different results: *.std.iq: StandardComponentSupplier *.dart.iq: DartComponentSupplier *.msq.iq: StandardMSQComponentSupplier
I think #17915 might fix the issue you are seeing. |
2) | ||
OR s_int IS NULL) | ||
AND (ip4_match(c, c) IS NOT NULL); | ||
No match found |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does No match found
mean?
since it supposed to be part of an Exception could we have a more details about the problem?
!ok | ||
|
||
#------------------------------------------------------------------------- | ||
# TESTCASE: test001 TEST_ID: A02 TYPE: POSITIVE TEST |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this TYPE:
part is redundant: it has no real value as the test has some expectation like !ok
- which should document the expected outcome already
!ok | ||
|
||
#------------------------------------------------------------------------- | ||
# Total query count 283 Positive tests: 135 Negative tests: 148 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we have more cases and less queries per file?
SELECT c | ||
FROM test_unnest, | ||
unnest(s_int) AS u(c); | ||
Cannot apply |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does Cannot apply
mean here? it should be more readable why this doesn't work
!ok | ||
|
||
#------------------------------------------------------------------------- | ||
# Total query count 43 Positive tests: 37 Negative tests: 6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think these headers are usefull - instead they could cause confusion:
what happens if tomorrow one more NEGATIVE
tests will be supported...should these numbers be adjusted as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
large files should not arrive like this! see other comment
"type" : "local", | ||
"baseDir" : "sql/src/test/quidem/qatests/kttm_nested/data", | ||
"filter" : "kttm-nested-v2-2019-08-25.json.gz" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should find a way to access the already accessible kttm-nested-v2-2019-08-25.json
on the classpath; and that should be the way to get larger datafiles
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the equivalent of !use druidtest:///?componentSupplier=KttmNestedComponentSupplier
if to use this dataset for AllDruidEnginesComponentSupplier
, DartComponentSupplier
, StandardMSQComponentSupplier
, and StandardComponentSupplier
? These tests originally used !use druidtest:///?componentSupplier=KttmNestedComponentSupplier
. We need to make them run for all 3 engines, but I couldn't find a way to do so. That's why the dataset was added.
Tried the latest code. It still OOMed. |
Add 2 tests for debugging Dart and MSQ in Quidem. Do not merge.