You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Detected the same issue with csv format without nested: V1
POST http://localhost:9200/_plugins/_sql?format=csv
{
"query" : "select * from account where account_number = 70",
"legacy": 1
}
account_number,firstname,address,balance,gender,city,employer,state,age,email,lastname
70,Deidre,685 School Lane,38172,F,Chestnut,Netplode,GA,33,deidrethompson@netplode.com,Thompson
V2
POST http://localhost:9200/_plugins/_sql?format=csv
{
"query" : "select * from account where account_number = 70"
}
account_number,firstname,address,balance,gender,city,employer,state,age,email,lastname
70,Deidre,
685 School Lane,
38172,F,Chestnut,Netplode,GA,
33,deidrethompson@netplode.com,Thompson
I've narrowed down that this bug is caused by the fact in legacy the header defines the content-type as text/plain; charset=UTF-8 while in the new engine the content-type is application/json; charset=UTF-8
What is the bug?
When using the
raw
orcsv
format output in SQL plugin, we expect each row of output to correspond with a row from the response.for example, from
SELECT nested(message.info), nested(comment.data) FROM nested_with_nulls
:Expected output:
Actual output:
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: