yutannihilation commented on issue #264: URL: https://github.com/apache/sedona-db/issues/264#issuecomment-3471158533
> This is how it works now in SedonaDB SQL: https://sedona.apache.org/sedonadb/latest/reference/sql/. Oh, thanks, I simply didn't notice `FROM` clause already allows a path to a JSON/CSV file. > ST_Read is more like a DuckDB's own syntax for GDAL. We can have a similar one for all cases but we don't need to maintain the same API as DuckDB Totally agreed! > * We focused on providing `read_xxx()` functions in Python/R before SQL because they're easier to use and easier for a user to access the documentation while typing the code. Conceptually the arguments are the same. Thanks for clarifying. This sounds reasonable to me. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
