AMashenkov commented on code in PR #2214:
URL: https://github.com/apache/ignite-3/pull/2214#discussion_r1245119135
##########
modules/runner/src/integrationTest/java/org/apache/ignite/internal/sql/api/ItCommonApiTest.java:
##########
@@ -120,6 +122,27 @@ public void testSessionExpiration() throws Exception {
ses2.execute(null, "SELECT 2 + 2").close();
}
+ /** Check correctness of planning timeout. */
+ @Test
+ public void testPlanningTimeout() {
+ IgniteSql sql = igniteSql();
+
+ sql("CREATE TABLE TST1(id INTEGER PRIMARY KEY, val INTEGER)");
+
+ Long oldPlannerTimeout = (Long)
IgniteTestUtils.getFieldValue(queryProcessor(), SqlQueryProcessor.class,
"plannerTimeout");
Review Comment:
Can we introduce 'plannerTimeout' option and pass it e.g. via session?
Or use system property instead of reflection hack.
--
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: notifications-unsubscr...@ignite.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
