[
https://issues.apache.org/jira/browse/ASTERIXDB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205878#comment-15205878
]
Chris Hillery commented on ASTERIXDB-1361:
------------------------------------------
Certainly "internal error" isn't very useful. This thing you're asking it to do
IS an error, however - Asterix can't provide CSV headers without a priori
knowledge of the form of the results, which is what the "output-record-type"
annotation is for. What we need is a more useful error message.
I've proposed a change (https://asterix-gerrit.ics.uci.edu/#/c/741/) which adds
this with the language "Cannot output CSV with header without specifying
output-record-type". One small issue is that this gets reported as
"SyntaxError: ..." which seems odd to me. It seems like any AsterixException
during query execution gets reported as such. Will see if there's an easy fix
to that too.
> CSV (with header) broken in ADM/AQL 101
> ----------------------------------------
>
> Key: ASTERIXDB-1361
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1361
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: AsterixDB, Data Formats, Web Interface
> Environment: AsterixDB on OSX through Web interface in Firefox
> Reporter: Michael J. Carey
> Assignee: Chris Hillery
>
> Try typing 1+1 to AsterixDB with CSV (with header) selected as the format.
> It causes an INTERNAL ERROR.
> Nothing should ever cause an internal error.
> :-)
> Also try typing {"name":"Mike", "salary":100}.
> This also gets the same internal error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
