main

GGitHubfeat: add support for reading json arrays (#4844)

dfe0861f创建于 2025年7月26日历史提交

文件	最后提交记录	最后更新时间
baddata1.json	feat: add support for reading json arrays (#4844) ## Changes Made General approach is that we peek at the first byte of the file. if it's [ we use the array algorithm, if its { we use the default ndjson algo. ⚠️ It's worth noting that this is not highly optimized and _could_ OOM on very large JSON files as they are pulled **entirely** into memory. as a side note: Our JSON reading logic is a total mess and I didn't want to do any unnecessary refactors, so there was a bit of copy/paste in this PR to get things to work. ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> ## Checklist - [ ] Documented in API Docs (if applicable) - [ ] Documented in User Guide (if applicable) - [ ] If adding a new documentation page, doc is added to docs/mkdocs.yml navigation - [ ] Documentation builds and is formatted properly (tag @/ccmao1130 for docs review)	1 年前
empty	feat: add support for reading json arrays (#4844) ## Changes Made General approach is that we peek at the first byte of the file. if it's [ we use the array algorithm, if its { we use the default ndjson algo. ⚠️ It's worth noting that this is not highly optimized and _could_ OOM on very large JSON files as they are pulled **entirely** into memory. as a side note: Our JSON reading logic is a total mess and I didn't want to do any unnecessary refactors, so there was a bit of copy/paste in this PR to get things to work. ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> ## Checklist - [ ] Documented in API Docs (if applicable) - [ ] Documented in User Guide (if applicable) - [ ] If adding a new documentation page, doc is added to docs/mkdocs.yml navigation - [ ] Documentation builds and is formatted properly (tag @/ccmao1130 for docs review)	1 年前
sample1.json	feat: add support for reading json arrays (#4844) ## Changes Made General approach is that we peek at the first byte of the file. if it's [ we use the array algorithm, if its { we use the default ndjson algo. ⚠️ It's worth noting that this is not highly optimized and _could_ OOM on very large JSON files as they are pulled **entirely** into memory. as a side note: Our JSON reading logic is a total mess and I didn't want to do any unnecessary refactors, so there was a bit of copy/paste in this PR to get things to work. ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> ## Checklist - [ ] Documented in API Docs (if applicable) - [ ] Documented in User Guide (if applicable) - [ ] If adding a new documentation page, doc is added to docs/mkdocs.yml navigation - [ ] Documentation builds and is formatted properly (tag @/ccmao1130 for docs review)	1 年前
sample1.jsonl	feat(sql): supports array of paths in read_ table-value functions (#3835) This is a small PR which supports an array of paths in the table-value functions: read_json, read_csv, and read_parquet. **Examples** sql SELECT * FROM read_json([ '/path/to/part1.json', '/path/to/part2.json' ]) -- ditto for read_csv and read_parquet	1 年前
sample2.json	feat: add support for reading json arrays (#4844) ## Changes Made General approach is that we peek at the first byte of the file. if it's [ we use the array algorithm, if its { we use the default ndjson algo. ⚠️ It's worth noting that this is not highly optimized and _could_ OOM on very large JSON files as they are pulled **entirely** into memory. as a side note: Our JSON reading logic is a total mess and I didn't want to do any unnecessary refactors, so there was a bit of copy/paste in this PR to get things to work. ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> ## Checklist - [ ] Documented in API Docs (if applicable) - [ ] Documented in User Guide (if applicable) - [ ] If adding a new documentation page, doc is added to docs/mkdocs.yml navigation - [ ] Documentation builds and is formatted properly (tag @/ccmao1130 for docs review)	1 年前
sample2.jsonl	feat(sql): supports array of paths in read_ table-value functions (#3835) This is a small PR which supports an array of paths in the table-value functions: read_json, read_csv, and read_parquet. **Examples** sql SELECT * FROM read_json([ '/path/to/part1.json', '/path/to/part2.json' ]) -- ditto for read_csv and read_parquet	1 年前