We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The docs do not indicate what the column from each format when using https://clickhouse.com/docs/en/sql-reference/table-functions/file
For example using 'LineAsString' returns the line column. Nowhere (that I could reasonably find) is this documented.
line
The shortcut was to make a crap tiny file and print out the select so I could see what the columns are.
I am also not sure there is a function to read the columns returned by a subquery so that I could use a query to inspect it like:
select columns(select * from file('...', 'LineAsString'))
The text was updated successfully, but these errors were encountered:
Ok so they are not listed in https://clickhouse.com/docs/en/interfaces/formats#lineasstring
but listed in https://clickhouse.com/docs/en/interfaces/schema-inference#line-as-string
Would assume some inter-linking
Sorry, something went wrong.
I think we can link from https://clickhouse.com/docs/en/interfaces/formats to https://clickhouse.com/docs/en/interfaces/schema-inference where appropriate with the comment
"For how this format behaves with schema inference see here)"
I'm not sure we can cleanly link in the other direction @danthegoodman1 hopefully this is sufficient and would have helped in your case.
Yeah please link that schema-inference one!
gingerwizard
No branches or pull requests
The docs do not indicate what the column from each format when using https://clickhouse.com/docs/en/sql-reference/table-functions/file
For example using 'LineAsString' returns the
line
column. Nowhere (that I could reasonably find) is this documented.The shortcut was to make a crap tiny file and print out the select so I could see what the columns are.
I am also not sure there is a function to read the columns returned by a subquery so that I could use a query to inspect it like:
The text was updated successfully, but these errors were encountered: