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
There have been changes in how table providers are registered so this is likely a regression. It would be good to get some regression tests added when we fix this.
I am guessing that the fix is simply to add NDJSON to this code in datafusion-cli:
Activity
andygrove commentedon Nov 14, 2022
There have been changes in how table providers are registered so this is likely a regression. It would be good to get some regression tests added when we fix this.
I am guessing that the fix is simply to add
NDJSONto this code in datafusion-cli:thomas-k-cameron commentedon Nov 16, 2022
What do you think about adding several test-cases for the datafusion-cli to check if some features works as intended?
Is there a directory intended for adding test-cases for the cli?(I couldn't find it/)
timvw commentedon Nov 16, 2022
Seems to have been gone missing in #1010
timvw commentedon Nov 17, 2022
Seems that this now available as regular "json" format:
https://github.com/apache/arrow-datafusion/blob/master/datafusion/core/src/datasource/file_format/json.rs#L46
The following works on my machine:
I have updated PR-4427 such that both JSON and NDJSON are registered by default
thomas-k-cameron commentedon Nov 23, 2022
I'm closing this issue because the problem has been fixed with PR-4427.