[jira] [Commented] (KUDU-424) Kudu CLI/shell for DDL and basic DML
[ https://issues.apache.org/jira/browse/KUDU-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713582#comment-15713582 ] Todd Lipcon commented on KUDU-424: -- Yea, I think it's reasonable to close this. Another point is that the Python integration is now pretty full-featured and is pretty useful when you just want to "poke at" a table and dont have any other software installed. > Kudu CLI/shell for DDL and basic DML > > > Key: KUDU-424 > URL: https://issues.apache.org/jira/browse/KUDU-424 > Project: Kudu > Issue Type: New Feature > Components: client, ops-tooling >Affects Versions: M5 >Reporter: Todd Lipcon >Priority: Critical > Labels: kudu-roadmap > > Currently there is basically no way to access Kudu aside from programmatic > APIs. We need to have some simple ability to do basic tasks from the command > line: > - create/drop/alter table > - scan a table/key range > - stretch goal: insert/delete/update -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KUDU-424) Kudu CLI/shell for DDL and basic DML
[ https://issues.apache.org/jira/browse/KUDU-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713246#comment-15713246 ] Dan Burkert commented on KUDU-424: -- Can we close this? As far as I know there are two options for a Kudu DDL shell, both of which are being developed outside the project: * [Impala|https://impala.apache.org/] * [ksql|https://github.com/danburkert/ksql] The fact that we haven't moved on this in more than two years is a pretty strong indication that we aren't going to develop a CLI from scratch in-tree. Perhaps we could reopen if an out-of-tree developed CLI tool wants to move into the Kudu project. > Kudu CLI/shell for DDL and basic DML > > > Key: KUDU-424 > URL: https://issues.apache.org/jira/browse/KUDU-424 > Project: Kudu > Issue Type: New Feature > Components: client, ops-tooling >Affects Versions: M5 >Reporter: Todd Lipcon >Priority: Critical > Labels: kudu-roadmap > > Currently there is basically no way to access Kudu aside from programmatic > APIs. We need to have some simple ability to do basic tasks from the command > line: > - create/drop/alter table > - scan a table/key range > - stretch goal: insert/delete/update -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KUDU-424) Kudu CLI/shell for DDL and basic DML
[ https://issues.apache.org/jira/browse/KUDU-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605118#comment-15605118 ] Gordon Gardiner commented on KUDU-424: -- Please include support for specifying the encoding and compression options for columns when creating or altering a table. > Kudu CLI/shell for DDL and basic DML > > > Key: KUDU-424 > URL: https://issues.apache.org/jira/browse/KUDU-424 > Project: Kudu > Issue Type: New Feature > Components: client, ops-tooling >Affects Versions: M5 >Reporter: Todd Lipcon >Priority: Critical > Labels: kudu-roadmap > > Currently there is basically no way to access Kudu aside from programmatic > APIs. We need to have some simple ability to do basic tasks from the command > line: > - create/drop/alter table > - scan a table/key range > - stretch goal: insert/delete/update -- This message was sent by Atlassian JIRA (v6.3.4#6332)