[
https://issues.jboss.org/browse/TEIID-2141?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2141.
-----------------------------------
Resolution: Done
Completed the implementation as shown in the previous comment, but opted for
teiid_row_number instead of teiid_rowcount. Also updated the docs/release notes.
To touch on the authorization added, there are two mechanisms for controlling access to
languages. First there needs to be a vdb property allowed-languages that uses a comma
separated list of case sensitive (since JSR-223 is case sensitive) names. Then if data
roles are used, the role will need a LANGUAGE permission specifying the language name.
Note in the vdb-deployer.xsd that no other permission actions can be granted if using the
language permission.
It would be more proper to have a USAGE permission - but our permission logic is based
upon just resource name and does not include resource type. We should address this at
some point to make it explicit that a permission affects a TABLE, PROCEDURE, SCHEMA,
LANGUAGE, FUNCTION, etc. It is possible now to have conflicting schema/table or
table/procedure names, so I'll log another issue to address this.
create an objecttable table function
------------------------------------
Key: TEIID-2141
URL:
https://issues.jboss.org/browse/TEIID-2141
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Analogous to xmltable, we should offer an objecttable function to get values off of an
object. The choice of scripting/path language could even be configurable. This would
help eliminate some of the common complexity of relational-object translations and can be
used to perform denoralization without a join - and could be first implemented to in
databasemetadata views to speed up databasemetadata query processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira