[JBoss JIRA] Commented: (TEIID-254) Metadata query for procedure columns needs work
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-254?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIID-254:
--------------------------------------
The simplest fix would be to change the System.ProcedureParams query from
SELECT DISTINCT p.ModelName, PROC_NAME AS ProcedureName, pp.NAME AS Name, RUNTIME_TYPE_NAME AS DataType, POSITION, lookup('SystemPhysical.PROC_PARAM_TYPE_ENUM', 'NAME', 'CODE', DIRECTION) AS Type, is_optional AS Optional, PRECISION, LENGTH AS TypeLength, SCALE, RADIX, lookup('SystemPhysical.NULL_TYPE_ENUM', 'NAME', 'CODE', NULL_TYPE) AS NullType FROM (SELECT SystemPhysical.PROC_PARAMS.PROC_NAME, SystemPhysical.PROC_PARAMS.NAME, SystemPhysical.PROC_PARAMS.RUNTIME_TYPE_NAME, SystemPhysical.PROC_PARAMS.POSITION, convert(SystemPhysical.PROC_PARAMS.DIRECTION, integer) AS DIRECTION, SystemPhysical.PROC_PARAMS.IS_OPTIONAL, SystemPhysical.PROC_PARAMS.PRECISION, SystemPhysical.PROC_PARAMS.LENGTH, SystemPhysical.PROC_PARAMS.SCALE, SystemPhysical.PROC_PARAMS.RADIX, SystemPhysical.PROC_PARAMS.NULL_TYPE, SystemPhysical.PROC_PARAMS.PROC_UUID FROM SystemPhysical.PROC_PARAMS UNION ALL SELECT rs.PROC_NAME, c.NAME, c.RUNTIME_TYPE_NAME, c.POSITION, 4, {b'false'}, c.PRECISION, c.LENGTH, c.SCALE, c.RADIX, c.NULL_TYPE, rs.PROC_UUID FROM SystemPhysical.PROC_RESULT_SETS AS rs, SystemPhysical.COLUMNS AS c WHERE rs.UUID = c.PARENT_UUID) AS pp, System.Procedures AS p WHERE PROC_UUID = p.UID
to
SELECT DISTINCT p.ModelName, p.FullName AS ProcedureName, pp.NAME AS Name, RUNTIME_TYPE_NAME AS DataType, POSITION, lookup('SystemPhysical.PROC_PARAM_TYPE_ENUM', 'NAME', 'CODE', DIRECTION) AS Type, is_optional AS Optional, PRECISION, LENGTH AS TypeLength, SCALE, RADIX, lookup('SystemPhysical.NULL_TYPE_ENUM', 'NAME', 'CODE', NULL_TYPE) AS NullType FROM (SELECT SystemPhysical.PROC_PARAMS.NAME, SystemPhysical.PROC_PARAMS.RUNTIME_TYPE_NAME, SystemPhysical.PROC_PARAMS.POSITION, convert(SystemPhysical.PROC_PARAMS.DIRECTION, integer) AS DIRECTION, SystemPhysical.PROC_PARAMS.IS_OPTIONAL, SystemPhysical.PROC_PARAMS.PRECISION, SystemPhysical.PROC_PARAMS.LENGTH, SystemPhysical.PROC_PARAMS.SCALE, SystemPhysical.PROC_PARAMS.RADIX, SystemPhysical.PROC_PARAMS.NULL_TYPE, SystemPhysical.PROC_PARAMS.PROC_UUID FROM SystemPhysical.PROC_PARAMS UNION ALL SELECT c.NAME, c.RUNTIME_TYPE_NAME, c.POSITION, 4, {b'false'}, c.PRECISION, c.LENGTH, c.SCALE, c.RADIX, c.NULL_TYPE, rs.PROC_UUID FROM SystemPhysical.PROC_RESULT_SETS AS rs, SystemPhysical.COLUMNS AS c WHERE rs.UUID = c.PARENT_UUID) AS pp, System.Procedures AS p WHERE PROC_UUID = p.UID
so that the the searchable p.FullName is used as the ProcedureName.
> Metadata query for procedure columns needs work
> -----------------------------------------------
>
> Key: TEIID-254
> URL: https://jira.jboss.org/jira/browse/TEIID-254
> Project: Teiid
> Issue Type: Task
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Fix For: 6.2.0
>
>
> Defect Tracker #24885: Even if procedure name criteria is supplied for the QUERY_PROCEDURE_COLUMNS, it is applied to a synthetic column - which can only be processed after all rows are retrieved. It looks like there may be other procedure name values in the system tables that would be a better place for this criteria (or at least more join criteria could be added under the ProcedureParams query)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Commented: (TEIID-259) Create Teiid Server Kit
by Ramesh Reddy (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-259?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIID-259:
------------------------------------
The build scripts are modified such that current "embedded" kit can be used in multi purpose, either in either "embedded" mode or in standalone server mode. The way user enables the environment defines how the run time is started.
1) If the specifies the embedded specific URL, the runtime is loaded into host JVM, and user has Teiid Embedded
2) If server is manually started, and user uses the Server specific, the client program can connect to Teiid Server instance over the socket.
Startup scripts for running the server are provided in the "bin" folder. There may additional scripts coming to this folder depending upon the user feed back. All the configuration is defined in the "deploy.properties". Currently there are no documentation on how this woks, however by the time 6.2 is released they will be provided.
One notable difference from legacy Server is the SOAP related web services, will not be supported in new Teiid runtime environment, these capabilities are provided through additional JBoss tools. Look at TEIID-673
> Create Teiid Server Kit
> -----------------------
>
> Key: TEIID-259
> URL: https://jira.jboss.org/jira/browse/TEIID-259
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 6.0.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 6.2.0
>
>
> Build a server kit and corresponding configuration installer for the server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Updated: (TEIID-218) Security URL properties handling
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-218?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-218:
---------------------------------
Fix Version/s: 6.3.0
(was: 6.2.0)
Moving security enhancements from clients to the 6.3 release. They are not critical for 6.3 and are not for typical use cases.
> Security URL properties handling
> --------------------------------
>
> Key: TEIID-218
> URL: https://jira.jboss.org/jira/browse/TEIID-218
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver, Server
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.3.0
>
>
> Defect Tracker #24196: Security URL properties are currently a mess in that there are three properties, clientToken, credentials, and trustedPayload that are all eventually treated at the trustedPayload. This is not desirable. Instead we should pass all of the connection properties to the membership service (as a map) for access by membership domains. This would remove the need to specifically pass the trustedPayload and application name as parameters. This could also be done for connectors provided that the message or the transport containing the connection properties is encrypted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months