[jira] [Issue Comment Deleted] (TAJO-1071) should be possible to get long query results with no prompt

["Niv Zvi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAJO-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niv Zvi updated TAJO-1071:
--------------------------
    Comment: was deleted

(was: Thanks for getting back to me so quickly!
I was familiar with -c and -f, I wasn't familiar with the syntax that you used, adding the column names, when I try it like you did I get an exception since the cli expects a database name:

tsql -c "select * from supplier" s_suppkey
Exception in thread "main" com.google.protobuf.ServiceException: org.apache.tajo.cli.InvalidClientSessionException: ERROR: database "s_suppkey" does not exist
        at org.apache.tajo.rpc.ServerCallable.withRetries(ServerCallable.java:105)
        at org.apache.tajo.client.TajoClient.getCurrentDatabase(TajoClient.java:198)
        at org.apache.tajo.cli.TajoCli.<init>(TajoCli.java:173)

Even if that worked, I cannot use it since I cannot force users of the scheduler to write their -c in a specific format. They will probably use it like in your doc examples, just "select * from supplier". Furthermore, we would like to give them the option to provide a file, then I would have to parse through that file to discover all the columns names in all queries and this is not possible.

 


)

> should be possible to get long query results with no prompt
> -----------------------------------------------------------
>
>                 Key: TAJO-1071
>                 URL: https://issues.apache.org/jira/browse/TAJO-1071
>             Project: Tajo
>          Issue Type: Improvement
>          Components: cli
>    Affects Versions: 0.8.0
>            Reporter: Niv Zvi
>            Priority: Minor
>
> Hi,
> I need to be able to run queries in batch mode, however, when the query result is long, I get a message to that I need to conform in order to continue:
> continue... ('q' is quit)
> If I run this using my scheduler, the job gets stuck.
> Is it possible to add a way to override this limitation and get the entire query result back?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)