You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Pochatkin (Jira)" <ji...@apache.org> on 2022/06/15 11:13:00 UTC
[jira] [Created] (IGNITE-17172) Create new command frontend for REPL mode
Mikhail Pochatkin created IGNITE-17172:
------------------------------------------
Summary: Create new command frontend for REPL mode
Key: IGNITE-17172
URL: https://issues.apache.org/jira/browse/IGNITE-17172
Project: Ignite
Issue Type: Improvement
Reporter: Mikhail Pochatkin
Currently all commands for both non-REPL and REPL mode has same frontend Picocli. It means that options parsing and mapping to command description is Picocli relationship.
Command logic is not related to frontend, relationship of frontend is split incoming command line and put all command option to next layer to process command execution.
In reality Picocli frontend for REPL command is not suitable by few reasons:
# In plans support interactive fill for required options. For example
{code:java}
cli> node connect
Q:Do you want to connect last node? (last-node-url) Y/n?
A: Y Output:
Connected to last-node-url! {code}
Picocli doesn't provide possibility to customize logic about command parsing and spliting to options.
# In current implementation SQL REPL didn't use Picocli frontend because its impossible to map all possible SQL queries to different Picocli CmdDesc but its is not needed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)