ozankabak commented on issue #6251:
URL:
https://github.com/apache/arrow-datafusion/issues/6251#issuecomment-1545663982
What do you think about a syntax like `CREATE [UNBOUNDED] EXTERNAL TABLE
...` (or the same with `INFINITE`)? For some reason having a lonely INFINITE or
UNBOUNDED keyword bothers me.
To summarize, my order of preference is:
1. `CREATE [UNBOUNDED/INFINITE] EXTERNAL TABLE ...`
2. `CREATE EXTERNAL TABLE ... OPTIONS('UNBOUNDED/INFINITE' 'TRUE')`
3. `CREATE EXTERNAL TABLE ... UNBOUNDED/INFINITE ... LOCATION
'tests/data/empty.csv'`
In terms of the UNBOUNDED vs INFINITE distinction, I think both are fine,
and we use them interchangeably in code. However, in the API, we should stick
to one and use it uniformly. At SQL API level, my tendency is towards UNBOUNDED.
--
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]
