[ https://jira.jboss.org/browse/TEIID-950?page=com.atlassian.jira.plugin.sy... ]
Ramesh Reddy updated TEIID-950:
-------------------------------
Fix Version/s: 7.1
> Add ability to control access to environment variables
> ------------------------------------------------------
>
> Key: TEIID-950
> URL: https://jira.jboss.org/browse/TEIID-950
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Environment: Found by client on MMx 502, tested and found issue present through 551.
> Reporter: Marc Shirley
> Fix For: 7.1
>
>
> SELECT ENV('os.name') || ' ' || ENV('os.version') || ' ' || ENV('java.home') returns the details of the server, which from the client perspective is a security risk. This information is even visible by a user with no access to any tables. Client is looking to have this disabled, or have the ability to disable it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-982?page=com.atlassian.jira.plugin.sy... ]
Ramesh Reddy updated TEIID-982:
-------------------------------
Fix Version/s: 7.1
> Materialized Views should be treated as a service in MMx through the Console
> ----------------------------------------------------------------------------
>
> Key: TEIID-982
> URL: https://jira.jboss.org/browse/TEIID-982
> Project: Teiid
> Issue Type: Feature Request
> Components: Jopr Plugin
> Reporter: Marc Shirley
> Fix For: 7.1
>
>
> Should be a service, controlled in Console, logs controlled by Log Settings, viewable by Log Viewer. There should also be a way to verify success/failure, last run time, from within Console. This could also be linked into the scheduling service (JBEDSP-144) if that existed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-1094?page=com.atlassian.jira.plugin.s... ]
Steve Hawkins updated TEIID-1094:
---------------------------------
Fix Version/s: 7.0
Affects Version/s: 6.0.0
> XML literal input to HTTP-SOAP connector is being URL encoded
> -------------------------------------------------------------
>
> Key: TEIID-1094
> URL: https://jira.jboss.org/browse/TEIID-1094
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 6.0.0
> Reporter: Debbie Steigner
> Fix For: 7.0
>
> Attachments: test.vdb
>
>
> Try to invoke a web service operation that takes an XML string as one of its parameters. Whenever you pass an XML string as input, MetaMatrix URL encoding to escape all the special characters. In other words, we escape the "<"'s to "<", etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-1094?page=com.atlassian.jira.plugin.s... ]
Steve Hawkins resolved TEIID-1094.
----------------------------------
Resolution: Out of Date
The ingest service is using a post and should not be encoding the document. The new jax-ws code will only encode values for get query strings.
> XML literal input to HTTP-SOAP connector is being URL encoded
> -------------------------------------------------------------
>
> Key: TEIID-1094
> URL: https://jira.jboss.org/browse/TEIID-1094
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Debbie Steigner
> Attachments: test.vdb
>
>
> Try to invoke a web service operation that takes an XML string as one of its parameters. Whenever you pass an XML string as input, MetaMatrix URL encoding to escape all the special characters. In other words, we escape the "<"'s to "<", etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-32?page=com.atlassian.jira.plugin.sys... ]
Steve Hawkins resolved TEIID-32.
--------------------------------
Resolution: Won't Fix
See TEIID-1097 for an alternative approach that allows for null values.
> Support null values in proc relational joins
> --------------------------------------------
>
> Key: TEIID-32
> URL: https://jira.jboss.org/browse/TEIID-32
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.x
> Reporter: Steven Hawkins
> Priority: Minor
> Fix For: 8.0
>
>
> Defect Tracker #24719: For dependent procedure executions to support null values we need to support criteria of the form:
> (value is not null and input = value) or (value is null and input is null)
> Currently this will not plan correctly because we do not recognize that the halfs of the conjunct are mutually exclusive and will not require 'or' support if the value is a reference and will have a known value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-1092?page=com.atlassian.jira.plugin.s... ]
Steve Hawkins commented on TEIID-1092:
--------------------------------------
Procedures do not have access to session level temp tables. There is no metadata for session level temp tables at design time. A workaround along the same lines would be to have a source table designated for global values. We'd have to investigate what would be appropriate for global or at least session global variables.
> Request to have Global Variables
> --------------------------------
>
> Key: TEIID-1092
> URL: https://jira.jboss.org/browse/TEIID-1092
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Debbie Steigner
> Assignee: Steve Hawkins
>
> Customer is requesting a Global Variable. They want the variable to persist outside of one procedure to other spawned procedures and subsequent queries.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-1095?page=com.atlassian.jira.plugin.s... ]
Steve Hawkins resolved TEIID-1095.
----------------------------------
Resolution: Out of Date
The logging has completely changed in teiid.
> Can 'java.net.SocketTimeoutException: Read timed out' be moved to WARNING instead of ERROR level
> ------------------------------------------------------------------------------------------------
>
> Key: TEIID-1095
> URL: https://jira.jboss.org/browse/TEIID-1095
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Since this ERROR simply indicates that a network level socket error has occurred and it is nothing to be alarmed about unless you are experiencing client-side errors indicating a connection has been broken, can it be changed to a WARNING.
> Error message:
> ERROR [CONTROLLER] SocketListener.run Error creating client connection.
> java.net.SocketTimeoutException: Read timed out
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-1096?page=com.atlassian.jira.plugin.s... ]
Van Halbert moved JBEDSP-180 to TEIID-1096:
-------------------------------------------
Project: Teiid (was: JBoss Enterprise Data Services Platform)
Key: TEIID-1096 (was: JBEDSP-180)
Component/s: Jopr Plugin
Server
(was: Designer)
Fix Version/s: (was: Future Versions)
> Allow cost analysis tool to work against custom connectors
> ----------------------------------------------------------
>
> Key: TEIID-1096
> URL: https://jira.jboss.org/browse/TEIID-1096
> Project: Teiid
> Issue Type: Feature Request
> Components: Jopr Plugin, Server
> Reporter: Marc Shirley
> Priority: Optional
>
> case 5541
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-1095?page=com.atlassian.jira.plugin.s... ]
Van Halbert moved JBEDSP-1200 to TEIID-1095:
--------------------------------------------
Project: Teiid (was: JBoss Enterprise Data Services Platform)
Key: TEIID-1095 (was: JBEDSP-1200)
Component/s: Server
(was: Server)
Fix Version/s: (was: Future Versions)
> Can 'java.net.SocketTimeoutException: Read timed out' be moved to WARNING instead of ERROR level
> ------------------------------------------------------------------------------------------------
>
> Key: TEIID-1095
> URL: https://jira.jboss.org/browse/TEIID-1095
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Since this ERROR simply indicates that a network level socket error has occurred and it is nothing to be alarmed about unless you are experiencing client-side errors indicating a connection has been broken, can it be changed to a WARNING.
> Error message:
> ERROR [CONTROLLER] SocketListener.run Error creating client connection.
> java.net.SocketTimeoutException: Read timed out
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/browse/TEIID-1095?page=com.atlassian.jira.plugin.s... ]
Van Halbert updated TEIID-1095:
-------------------------------
Note: jira.jboss.org/jira/browse/JBEDSP-1003 related to the same issue and similar changes.
> Can 'java.net.SocketTimeoutException: Read timed out' be moved to WARNING instead of ERROR level
> ------------------------------------------------------------------------------------------------
>
> Key: TEIID-1095
> URL: https://jira.jboss.org/browse/TEIID-1095
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Since this ERROR simply indicates that a network level socket error has occurred and it is nothing to be alarmed about unless you are experiencing client-side errors indicating a connection has been broken, can it be changed to a WARNING.
> Error message:
> ERROR [CONTROLLER] SocketListener.run Error creating client connection.
> java.net.SocketTimeoutException: Read timed out
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira