[jira] [Created] (IGNITE-18239) Fix completion for node config command in CLI repl.
Yury Yudin created IGNITE-18239:
---
Summary: Fix completion for node config command in CLI repl.
Key: IGNITE-18239
URL: https://issues.apache.org/jira/browse/IGNITE-18239
Project: Ignite
Issue Type: Bug
Components: cli
Reporter: Yury Yudin
{noformat}
[defaultNode]> node config update
--node-name -n -v compute raft
--verbose -u clientConnector network rest
{noformat}
We don't support changes to compute or raft here - seems these completions are
simply wrong.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18100) help command in CLI actually runs the command instead of giving help about it
[
https://issues.apache.org/jira/browse/IGNITE-18100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Yudin updated IGNITE-18100:
Summary: help command in CLI actually runs the command instead of giving
help about it (was: help cluster status actually runs cluster status instead
of giving help)
> help command in CLI actually runs the command instead of giving help about it
> -
>
> Key: IGNITE-18100
> URL: https://issues.apache.org/jira/browse/IGNITE-18100
> Project: Ignite
> Issue Type: Improvement
> Components: cli
>Reporter: Yury Yudin
>Priority: Major
> Labels: ignite-3
>
> help command actually tries to execute the actual command instead of giving
> help:
> {code:java}
> [demo1]> help cluster status
> [name: TEST, nodes: 1, status: active, cmgNodes: [demo1], msNodes: [demo1]]
> [demo1]> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18101) Add help for SQL commands
Yury Yudin created IGNITE-18101:
---
Summary: Add help for SQL commands
Key: IGNITE-18101
URL: https://issues.apache.org/jira/browse/IGNITE-18101
Project: Ignite
Issue Type: Improvement
Components: cli
Reporter: Yury Yudin
help in SQL REPL should actually give details about the syntax of SQL commands.
like:
> help create table
{color:#00}CREATE TABLE _table_name_ (
\{_}column1 datatype{_},
\{_}column2 datatype{_},
\{_}column3 datatype{_},
); {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18100) help cluster status actually runs cluster status instead of giving help
Yury Yudin created IGNITE-18100:
---
Summary: help cluster status actually runs cluster status instead
of giving help
Key: IGNITE-18100
URL: https://issues.apache.org/jira/browse/IGNITE-18100
Project: Ignite
Issue Type: Improvement
Components: cli
Reporter: Yury Yudin
help command actually tries to execute the actual command instead of giving
help:
{code:java}
[demo1]> help cluster status
[name: TEST, nodes: 1, status: active, cmgNodes: [demo1], msNodes: [demo1]]
[demo1]> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18099) Help improvements in CLI
Yury Yudin created IGNITE-18099: --- Summary: Help improvements in CLI Key: IGNITE-18099 URL: https://issues.apache.org/jira/browse/IGNITE-18099 Project: Ignite Issue Type: Epic Components: cli Reporter: Yury Yudin Currently help command in the ignite3 CLI is very rudimental and doesn't give much information about commands or SQL syntax. This epic is a collection of items to improve that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18098) ignite3 db should write logs into the logs folder.
Yury Yudin created IGNITE-18098:
---
Summary: ignite3 db should write logs into the logs folder.
Key: IGNITE-18098
URL: https://issues.apache.org/jira/browse/IGNITE-18098
Project: Ignite
Issue Type: Improvement
Components: build
Reporter: Yury Yudin
Currently ignite3db (executed from unpacked zip distro) appears to create an
empty .log file in the log directory, but most of the logs are still
written into the IGNITE_HOME/ignite3*.log files instead.
Should be written into the log directory instead.
{code:java}
demo@ymac ignite3-db-3.0.0-SNAPSHOT % l
./ README.md ignite3db-0.log.lck work/
../ bin/ lib/
LICENSE etc/ log/
NOTICE ignite3db-0.log pid
jjb@demo ignite3-db-3.0.0-SNAPSHOT % ll log
total 0
drwxr-xr-x 3 demo staff 96 7 Nov 08:51 .
drwxr-xr-x 13 demo staff 416 7 Nov 08:51 ..
-rw-r--r-- 1 demo staff 0 7 Nov 08:51 demo1.log
demo@ymac ignite3-db-3.0.0-SNAPSHOT % {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18097) CLI should check if it's already connected before trying to connect
Yury Yudin created IGNITE-18097:
---
Summary: CLI should check if it's already connected before trying
to connect
Key: IGNITE-18097
URL: https://issues.apache.org/jira/browse/IGNITE-18097
Project: Ignite
Issue Type: Improvement
Components: cli
Reporter: Yury Yudin
{code:java}
Do you want to reconnect to the last connected node http://localhost:10300?
[Y/n]
Connected to http://localhost:10300
Would you like to use http://localhost:10300 as the default URL? [Y/n]
Config saved
[demo1]> connect
Connected to http://localhost:10300
[demo1]> connect -v
--> GET http://localhost:10300/management/v1/configuration/node
<-- 200 OK http://localhost:10300/management/v1/configuration/node (2ms,
783-byte body)
--> GET http://localhost:10300/management/v1/node/state
<-- 200 OK http://localhost:10300/management/v1/node/state (1ms, 35-byte body)
Connected to http://localhost:10300
[demo1]> {code}
Currently CLI is trying to connect again even if it's already connected. It
should check and report "already connected" if the node we're trying to connect
to is the same. Otherwise it should ask the user if he's sure to connect to a
different node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18096) ignite3db script should be more verbose on startup
Yury Yudin created IGNITE-18096:
---
Summary: ignite3db script should be more verbose on startup
Key: IGNITE-18096
URL: https://issues.apache.org/jira/browse/IGNITE-18096
Project: Ignite
Issue Type: Improvement
Components: build
Reporter: Yury Yudin
{code:java}
demo@mac ignite3-db-3.0.0-SNAPSHOT % ./bin/ignite3db start
demo@mac ignite3-db-3.0.0-SNAPSHOT % {code}
Currently successful start doesn't report anything which might be confusing to
the user. It should at least report that the node with the has started
successfully.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18095) Ignite3 db startup script should attempt to guess IGNITE_HOME if not set
Yury Yudin created IGNITE-18095:
---
Summary: Ignite3 db startup script should attempt to guess
IGNITE_HOME if not set
Key: IGNITE-18095
URL: https://issues.apache.org/jira/browse/IGNITE-18095
Project: Ignite
Issue Type: Improvement
Components: build
Reporter: Yury Yudin
{code:java}
demo@mac bin % ./ignite3db
./ignite3db: line 25:
/Users/demo/Ignite/Binaries/ignite3/ignite3-db-3.0.0-SNAPSHOT/bin/etc/bootstrap-config.env:
No such file or directory
demo@mac bin % {code}
It looks like the guess of IGNITE_HOME was incorrect and needs fixing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18039) Switch our build system to gradle
Yury Yudin created IGNITE-18039: --- Summary: Switch our build system to gradle Key: IGNITE-18039 URL: https://issues.apache.org/jira/browse/IGNITE-18039 Project: Ignite Issue Type: Epic Components: build Reporter: Yury Yudin As proposed and agreed as part of IEP-93 ignite3 build system is being switched to gradle. This epic is a collection of all tickets that need to be completed to make the switch to gradle as smooth as possible both in terms of building the artefacts as well as day-to-day development.The last item in this epic would be the removal of the original maven build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17469) cli profile commands unification
[
https://issues.apache.org/jira/browse/IGNITE-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Yudin updated IGNITE-17469:
Description:
cli config profile now has two commands show and create, while setting a
profile is done through a parameter, which is confusing.
There should be a separate command to set the profile.
In general I would suggest the commands there to look like:
cli config show
cli config set
cli config get
All repl cli commands should not accept --profile or -p parameters, all setting
and getting of the params in a profile should go through its activation
instead. I.e. cli config profile create newprofile ; cli config profile
activate newprofile; cli config set
ignite.cluster-url=[http://localhost:10300|http://localhost:10300/]
We should retain --profile in non-repl mode.
Profile manipulation should go like below:
cli config profile show []
cli config profile list
cli config profile create --copy-from
cli config profile activate
Let’s please update IEP with the corresponding changes as well.
Let's also make sure non-cli commands do have --profile option and
auto-completion scripts are updated accordingly. Currently I don't see any
suggestions on --profile there:
{noformat}
tests@ubuntu:~/Work/apache-ignite-3.0.0-SNAPSHOT$ ./ignite cluster config show
--profile te
st
Unknown options: '--profile', 'test'
Usage: ignite cluster config show [-h] [--cluster-url=]
[--selector=]
Shows cluster configuration.
--cluster-url=
Url to ignite node.
-h, --help Show this help message and exit.
--selector=
Configuration path selector.
tests@ubuntu:~/Work/apache-ignite-3.0.0-SNAPSHOT$
{noformat}
was:
cli config profile now has two commands show and create, while setting a
profile is done through a parameter, which is confusing.
There should be a separate command to set the profile.
In general I would suggest the commands there to look like:
cli config show
cli config set
cli config get
All repl cli commands should not accept --profile or -p parameters, all setting
and getting of the params in a profile should go through its activation
instead. I.e. cli config profile create newprofile ; cli config profile
activate newprofile; cli config set
ignite.cluster-url=[http://localhost:10300|http://localhost:10300/]
We should retain --profile in non-repl mode.
Profile manipulation should go like below:
cli config profile show []
cli config profile list
cli config profile create --copy-from
cli config profile activate
Let’s please update IEP with the corresponding changes as well.
> cli profile commands unification
>
>
> Key: IGNITE-17469
> URL: https://issues.apache.org/jira/browse/IGNITE-17469
> Project: Ignite
> Issue Type: Improvement
> Components: cli, ignite-3
>Reporter: Yury Yudin
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
>
> cli config profile now has two commands show and create, while setting a
> profile is done through a parameter, which is confusing.
> There should be a separate command to set the profile.
> In general I would suggest the commands there to look like:
> cli config show
> cli config set
> cli config get
> All repl cli commands should not accept --profile or -p parameters, all
> setting and getting of the params in a profile should go through its
> activation instead. I.e. cli config profile create newprofile ; cli config
> profile activate newprofile; cli config set
> ignite.cluster-url=[http://localhost:10300|http://localhost:10300/]
> We should retain --profile in non-repl mode.
> Profile manipulation should go like below:
> cli config profile show []
> cli config profile list
> cli config profile create --copy-from
> cli config profile activate
>
> Let’s please update IEP with the corresponding changes as well.
>
> Let's also make sure non-cli commands do have --profile option and
> auto-completion scripts are updated accordingly. Currently I don't see any
> suggestions on --profile there:
> {noformat}
> tests@ubuntu:~/Work/apache-ignite-3.0.0-SNAPSHOT$ ./ignite cluster config
> show --profile te
> st
> Unknown options: '--profile', 'test'
> Usage: ignite cluster config show [-h] [--cluster-url=]
> [--selector=]
> Shows cluster configuration.
> --cluster-url=
> Url to ignite node.
> -h, --help Show this help message and exit.
> --selector=
> Configuration path selector.
> tests@ubuntu:~/Work/apache-ignite-3.0.0-SNAPSHOT$
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17469) cli profile commands unification
Yury Yudin created IGNITE-17469: --- Summary: cli profile commands unification Key: IGNITE-17469 URL: https://issues.apache.org/jira/browse/IGNITE-17469 Project: Ignite Issue Type: Improvement Components: cli, ignite-3 Reporter: Yury Yudin cli config profile now has two commands show and create, while setting a profile is done through a parameter, which is confusing. There should be a separate command to set the profile. In general I would suggest the commands there to look like: cli config show cli config set cli config get All cli commands should not accept --profile or -p parameters, all setting and getting of the params in a profile should go through its activation instead. I.e. cli config profile create newprofile ; cli config profile activate newprofile; cli config set ignite.cluster-url=[http://localhost:10300|http://localhost:10300/] Profile manipulation should go like below: cli config profile show [] cli config profile list cli config profile create --copy-from cli config profile activate -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17348) Add quit/exit command to Ignite3 CLI sql REPL
Yury Yudin created IGNITE-17348: --- Summary: Add quit/exit command to Ignite3 CLI sql REPL Key: IGNITE-17348 URL: https://issues.apache.org/jira/browse/IGNITE-17348 Project: Ignite Issue Type: Task Components: cli Reporter: Yury Yudin turns out there is no way to exit from sql REPL in ignite3 CLI other than pressing Ctrl+D - while this works, a separate command to exit to the top REPL would be nice to have. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17347) Add port parameters to Ignite3 CLI node start command
Yury Yudin created IGNITE-17347: --- Summary: Add port parameters to Ignite3 CLI node start command Key: IGNITE-17347 URL: https://issues.apache.org/jira/browse/IGNITE-17347 Project: Ignite Issue Type: Task Components: cli Reporter: Yury Yudin Currently Ignite3 CLI node start command only provides a way to set different port parameters via supplying a different configuration file. This makes it somewhat cumbersome to start multple nodes on the same machine. Let's provide --port and --rest-port parameters to the node start command to make it easier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17346) Ignite3 CLI long output not readable in windows terminal
[
https://issues.apache.org/jira/browse/IGNITE-17346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Yudin updated IGNITE-17346:
Component/s: cli
> Ignite3 CLI long output not readable in windows terminal
>
>
> Key: IGNITE-17346
> URL: https://issues.apache.org/jira/browse/IGNITE-17346
> Project: Ignite
> Issue Type: Task
> Components: cli
>Reporter: Yury Yudin
>Priority: Major
> Labels: ignite-3
>
> When output of ignite3 command does not fit the window it scrolls and it's
> history is lost in the windows terminal. Scrolling up shows previous commands
> but not the output...
> {noformat}
> [disconnected]>
>
> "memoryAllocator" : {
> "type" : "unsafe"
> },
> "replacementMode" : "CLOCK",
> "size" : 268435456
> },
> "pageSize" : 16384,
> "regions" : [ ]
> },
> "rocksDb" : {
> "defaultRegion" : {
> "cache" : "lru",
> "numShardBits" : -1,
> "size" : 268435456,
> "writeBufferSize" : 67108864
> },
> "regions" : [ ]
> },
> "table" : {
> "defaultDataStorage" : "rocksdb",
> "tables" : [ ]
> }
> }
> [test1]>{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17346) Ignite3 CLI long output not readable in windows terminal
Yury Yudin created IGNITE-17346:
---
Summary: Ignite3 CLI long output not readable in windows terminal
Key: IGNITE-17346
URL: https://issues.apache.org/jira/browse/IGNITE-17346
Project: Ignite
Issue Type: Task
Reporter: Yury Yudin
When output of ignite3 command does not fit the window it scrolls and it's
history is lost in the windows terminal. Scrolling up shows previous commands
but not the output...
{noformat}
[disconnected]>
"memoryAllocator" : {
"type" : "unsafe"
},
"replacementMode" : "CLOCK",
"size" : 268435456
},
"pageSize" : 16384,
"regions" : [ ]
},
"rocksDb" : {
"defaultRegion" : {
"cache" : "lru",
"numShardBits" : -1,
"size" : 268435456,
"writeBufferSize" : 67108864
},
"regions" : [ ]
},
"table" : {
"defaultDataStorage" : "rocksdb",
"tables" : [ ]
}
}
[test1]>{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
