You define $select on the odata URL and define all the columns you want, or create another view of the same table without the that particular column exposed.

BTW, what is behavior through JDBC? If that is allowing "select *" and not returning the column, then we will consider the enhancement for OData.

Ramesh..

Try using JDBC client, like SQuirreL, if the same behavior then you can log a JIRA.

I think what you are seeing is that if you don't specify $select, the ODataSQLBuilder does not filter non selectable columns from the generated Teiid query (if we internally were using select * instead, then this would work as expected).  So yes that needs an issue to fix.

This was logged and worked as [TEIID-3698] non-selectable columns will cause OData failures - JBoss Issue Tracker

selectable or not, column masking is two different features. selectable defines if column can be selected, masking shows the column but can mask the data with whatever you want. If you want the column to show up for all users but show different values for each logged in user then column masking is what you are looking for.