-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
influx command: parsable output #6896
Comments
Have you tried using the
|
Using the
|
Seems reasonable enough to detect if the input is a TTY and allow something like |
I don't see how
From what I can see, the import format is not meant to be used for running arbitrary statements. |
Looks like I'm wrong. I'll mark this as a feature request and we'll add it to the list of things that needs to be done. |
Feature Request
Proposal:
The
influx
command should be able to produce output which can be parsed.Currently it produces a lot of garbage at the beginning of the output, and prefixes output lines with
>
.Current behavior:
Desired behavior:
This should either be controlled by a flag, such as
-quiet
, or by detecting whether STDOUT is a TTY.Use case:
It is currently very difficult to use the
influx
command in a script and parse the output because of all the extra noise that it outputs.The text was updated successfully, but these errors were encountered: