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
At the moment ES-SQL adopts a row based approach for returning the results, meaning a list of lists where each sub-list contains one value for each column/field.
The columnar approach, on the other hand, returns all values of a certain column in a single list. Still to be decided if all the variants of clients (ODBC, JDBC, REST etc) and formats (json, yaml, txt, csv etc) make sense for this feature.
The text was updated successfully, but these errors were encountered:
Kibana Canvas functions involving common renderers that use column JSONs themselves would benefit, as there'd be no need to expensively transpose big arrays in the browser, besides the all-around gain of better compressibility (due to negligible [ ] and lower , noise; serially adjacent data likely having the same format; common parts or, in the case of ordered output, identical values)
At the moment ES-SQL adopts a row based approach for returning the results, meaning a list of lists where each sub-list contains one value for each column/field.
The columnar approach, on the other hand, returns all values of a certain column in a single list. Still to be decided if all the variants of clients (ODBC, JDBC, REST etc) and formats (json, yaml, txt, csv etc) make sense for this feature.
The text was updated successfully, but these errors were encountered: