Github user kaspersorensen commented on the issue:
https://github.com/apache/metamodel/pull/163
I'm not opposed to _also_ adding better support for choosing your own table
names and such, but yes, the idea behind using the filename as table name was
to allow expansion of the logical DataContext either via CompositeDataContext
or maybe by a future implementation where a folder of files could be opened as
one schema.
When you mention "alias in the data context", you mean another Table with
TableType=ALIAS? I can see how that would make it really clear. OTOH that would
then have to be implemented on a data context basis rather than as a generic
construct in the parser. If I can draw a parallel to `SELECT *` then I would
say that this is a parsing/query level convenience that I find really useful
whenever I'm feeling lazy and don't want to figure out column names. I am kind
of hoping for something similar just for table names.
---
