Github user kaspersorensen commented on the pull request:
https://github.com/apache/metamodel/pull/82#issuecomment-165740056
That sounds a bit strange because only very specific query types do that.
For instance "primary key lookup" queries and "select count(*)" queries. But
OK, maybe your query is a primary key lookup with a scalar function on it?
Could be.
And I guess that really reveals the problem... That in
```executePrimaryKeyLookupQuery(...)``` we are _passing in_ the select item.
That used to be OK because select items wasn't that difficult. But now it
select item is more complicated. So maybe we should rather change the contract
so that ```executePrimaryKeyLookupQuery(...)```,
```materializeMainSchemaTable``` and any similar methods do NOT get a list of
select items, but instead get a list of columns. And then their results will be
generically postprocessed to add the scalar function layer on top.
---
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.
---
