[JBoss JIRA] (TEIID-2313) Same sql execution get some column data missing by use pure postgresql driver
by deshi xiao (JIRA)
deshi xiao created TEIID-2313:
---------------------------------
Summary: Same sql execution get some column data missing by use pure postgresql driver
Key: TEIID-2313
URL: https://issues.jboss.org/browse/TEIID-2313
Project: Teiid
Issue Type: Bug
Components: Common
Affects Versions: 7.6
Environment: teiid 7.6 rhel6.3 postgres-driver
Reporter: deshi xiao
Assignee: Steven Hawkins
Hi,teiid devleoper
I use rubygem-pg to connect the teiid server. but i found a weird issues. I got som column missing by postgresql, but the same sql execution got full column data in same source/same table. it depend on my private data expose concern. could you please give me your email, i can directly send my testing script to you. dxiao(a)redhat.com you can touch me in internal channel. thanks a lot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2316) Give translators a better batch size
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2316:
-------------------------------------
Summary: Give translators a better batch size
Key: TEIID-2316
URL: https://issues.jboss.org/browse/TEIID-2316
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.3
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
7.5 and later releases refined logic in the engine to shape batch sizes based upon the data, however we still only use the default connector batch size when requesting data.
This value currently defaults to 512, however that can be much too large for many scenarios given how the underlying sources handling buffering. At the least we should provide the engine adjusted batch size. It would be good as well to let the translator specify a scaling factor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2253) Multi-source isssues
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2253:
-------------------------------------
Summary: Multi-source isssues
Key: TEIID-2253
URL: https://issues.jboss.org/browse/TEIID-2253
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
The design of the multi-source feature has several issues that need addressed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2292) Add "SOURCE_NAME" column automatically for Multi-Source models
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2292:
-----------------------------------
Summary: Add "SOURCE_NAME" column automatically for Multi-Source models
Key: TEIID-2292
URL: https://issues.jboss.org/browse/TEIID-2292
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 8.2
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Currently Teiid adds SOURCE_NAME pseudo column when the model defines as multi-source to all the tables. This is not reflected in the metadata. However based on the community requests it looks like providing a way to automatically adding this to the tables and procedures is useful in dynamic vdb scenarios.
This can be added when a property like
<property name="multi-source-column" value="{name-of-column}"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2315) Multi-source metadata wrapper needs to distinguish between physical/virtual
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2315:
-------------------------------------
Summary: Multi-source metadata wrapper needs to distinguish between physical/virtual
Key: TEIID-2315
URL: https://issues.jboss.org/browse/TEIID-2315
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 8.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
With TEIID-2136 it was allowable to mix virtual entries on a physical model. The multi-source metadata wrapper is not aware of that distinction and will put a pseudo column on even the virtual entries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2254) Avoid name conflicts with source_name column
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2254:
-------------------------------------
Summary: Avoid name conflicts with source_name column
Key: TEIID-2254
URL: https://issues.jboss.org/browse/TEIID-2254
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Allow the multi-source column name to be configurable, or something more teiid specific, or use extension metadata, etc. to avoid name conflicts with source columns named source_name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (TEIID-669) Support "pass though" SQL commands to sources
by Ramesh Reddy (JIRA)
Support "pass though" SQL commands to sources
---------------------------------------------
Key: TEIID-669
URL: https://jira.jboss.org/jira/browse/TEIID-669
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 6.2.0
Currently there is no mechanism in Teiid, when a query is submitted to a runtime engine that is passed through the query engine unadulterated and unmodified and submitted directly to a source connector. All queries are parsed, optimized, re-written. Some times this limits the functionality in Teiid, when a user would like to execute a query that is very "source" specific. For example Oracle supports lots of Oracle specific functions that are not supported by the SQL spec, to support execution of these in Teiid user need to resort to UDF, which is cumbersome and involves modelling.
Another benefit of this is also to pass DDL to sources, currently since Teiid does not support DDL, this is not possible at all.
There is no-expectation that these queries are part of any data integration, these are one off queries that enhance user experience with Teiid if they use this feature. Command Payload mechanism is similar system that is used for authentication and authorization needs at the connector level, this feature can use similar techniques or use some custom extension to the language to define a query etc.
--
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
12 years, 10 months
[JBoss JIRA] (TEIID-2255) Allow for non-literal source_name values
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2255:
-------------------------------------
Summary: Allow for non-literal source_name values
Key: TEIID-2255
URL: https://issues.jboss.org/browse/TEIID-2255
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
The current design of multi-source requires that the source_name is a literal, which prevents more common usage patterns, such as a prepared statement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months