[
https://issues.apache.org/jira/browse/IGNITE-19729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-19729:
-------------------------------------
Fix Version/s: 2.16
> [ducktests] Support sqlConfiguration field in ignite configuration
> ------------------------------------------------------------------
>
> Key: IGNITE-19729
> URL: https://issues.apache.org/jira/browse/IGNITE-19729
> Project: Ignite
> Issue Type: Task
> Reporter: Sergey Korotkov
> Assignee: Sergey Korotkov
> Priority: Trivial
> Labels: ducktests
> Fix For: 2.16
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> To test the new calcite sql query engine the sqlConfiguration field in ignite
> configuration should be supported in ducktests.
> Additional small ducktests fixes were also included in scope:
> * Add ability to run arbitrary control.sh subcommand.
> * It appears that {{pgrep}} on some linuxes (centos) cuts long command lines
> (say with long list of jars in classpath) even if '-a' option is specified.
> So ducktape fails to detect the PID of the service java process. Rewrite via
> the {{ps}}.
> * One of the source of long command lines was a bug that IgniteSpec adds
> modules to service modules list each time the new node started. So say the
> 6th node gets command line with the same jar modules mentioned 6 times and
> the corresponing command line exceed limit for the {{pgrep}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
