Github user kaspersorensen commented on the pull request:
https://github.com/apache/metamodel/pull/55#issuecomment-146017943
As you can see on my todo-list above, actually now it works in JDBC also
and I have improved testing and all.
The only thing that doesn't work (that I know of) is having scalar
functions in e.g. the WHERE clause of a JDBC query. I couldn't yet figure out a
good way to decompose that problem. I can think of three solution scenarios:
1. Simply not support it, but throw a MetaModel exception when it is
attempted. For me this is actually OK to begin with.
1. Have a failover strategy when this happens which uses a
QueryPostprocessDataContext and thus eventually one or more full-table-scans to
execute the query.
1. Do something really clever to decompose the query and figure out how
much of it can be natively executed, do that, and postprocess the rest. This
seems very complex so I wouldn't recommend it for now.
What do you guys think? I prefer 1 or 2.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
