[JBoss JIRA] Created: (TEIID-429) Use DataSources in creating the ConnectorBindings instead of creating one using the Driver
by Ramesh Reddy (JIRA)
Use DataSources in creating the ConnectorBindings instead of creating one using the Driver
------------------------------------------------------------------------------------------
Key: TEIID-429
URL: https://jira.jboss.org/jira/browse/TEIID-429
Project: Teiid
Issue Type: Task
Affects Versions: 6.x
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.0.0
Currently when we have separate …
[View More]configurations for XA sources and Non-XA sources, these should be combined into one definition, and by default we should make attempt use the data sources instead of Drivers. This will make it easy on the user in specifying the properties rather than coming up with unique URL for the data source.
This will add
DatabaseName
ServerName
Port
properties in addition to already provided,
User
Password
URL -> expert=true
properties. The URL property will be set to "expert", so that if one needs to use the Driver, you can still use it. In addition this needs to provide support to add additional properties that may be needed by the specific data source. For this add
OptionalProperties
This should be supplied in the format [name=value;name=value] and runtime engines should support these to add these properties as DataSource bean properties.
--
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
[View Less]
14 years, 10 months
[JBoss JIRA] Created: (TEIID-563) Exporting the configuration, via console or utility, the configuration system properties now contains everything in the system, not just defined by the Configuration component type
by Van Halbert (JIRA)
Exporting the configuration, via console or utility, the configuration system properties now contains everything in the system, not just defined by the Configuration component type
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-563
URL: https://jira.jboss.org/jira/browse/TEIID-563
Project: Teiid
…
[View More] Issue Type: Bug
Components: Common
Affects Versions: 6.1.0
Reporter: Van Halbert
Assignee: Steven Hawkins
When exporting the configuration, using either the console or the configexport utility, the configuration properties segment now contains all the properties that exist when calling System.getProperties(), instead only what is defined by the Configuration component type.
--
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
[View Less]
14 years, 10 months
[JBoss JIRA] Created: (TEIID-605) Push down query results different than MetaMatrix query results without push down - Oracle 11
by Warren Gibson (JIRA)
Push down query results different than MetaMatrix query results without push down - Oracle 11
----------------------------------------------------------------------------------------------
Key: TEIID-605
URL: https://jira.jboss.org/jira/browse/TEIID-605
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Environment: Running Teiid Server on Windows
CTC Query testing client on Windows
…
[View More] Reporter: Warren Gibson
Assignee: Steven Hawkins
This may not be a bug but may just be a decision point to determine if MetaMatrix should guarantee the same query results as if the query was pushed down to the source. In some cases different results can be expected from different DBMS sources.
1. Running Teiid Server with Console Extension Capability Class set to default (blank).
2. Run queries against Oracle 11 source.
3. Results show many examples where "nulls" are being handled differently in a push down ORDER BY
situation than what our expected results reflect.
4. Basically in the Oracle 11 situation the "nulls" are showing up in the results
just opposite from what MetaMatrix does. In other words in the following query
"Select BQT1.SmallA.IntNum From BQT1.SmallA ORDER BY BQT1.SmallA.IntNum DESC" push down
results shows "nulls" at the beginning of results whereas without push down MetaMatrix
will show the "nulls" at the end of the results.
5. See attached results from this 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
[View Less]
14 years, 10 months
[JBoss JIRA] Created: (TEIID-745) Ensure string parsing routines are consistent
by Steven Hawkins (JIRA)
Ensure string parsing routines are consistent
---------------------------------------------
Key: TEIID-745
URL: https://jira.jboss.org/jira/browse/TEIID-745
Project: Teiid
Issue Type: Quality Risk
Components: Common, Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
String parsing strictness varies …
[View More]depending upon whether a convert or a parse function is used. In short we should:
1. Perform a trim prior to parsing (double and float converts already do this implicitly)
2. Use all non-whitespace characters in the parse string - the DateFormat, NumberFormat, and most of the convert methods allow for junk to appear after a successful parsing.
3. Time/Date/Timestamps should use non lenient parsing to disallow dates that are out of range, i.e. 2007-13-35
--
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
[View Less]
14 years, 10 months
[JBoss JIRA] Created: (TEIID-684) Dynamic data integration feature (Integrate data with out a VDB)
by Ramesh Reddy (JIRA)
Dynamic data integration feature (Integrate data with out a VDB)
----------------------------------------------------------------
Key: TEIID-684
URL: https://jira.jboss.org/jira/browse/TEIID-684
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Critical
Fix For: 6.3.0
This is feature …
[View More]request for dynamically integrating the data with out any modelling exercise, so that any tooling is not required before you can start integrating data.
Using this feature, the user would create/define a Connectors (data sources) in the Teiid runtime engine, and then user connects to runtime engine using the JDBC driver provided, then he/she can start writing SQL queries that spans multiple data sources in a single statement as if they are single source.
For example:
Data Source: A has
TableA1
TableA2
DataSource: B has
TableB1
TableB2
user can write SQL queries such as
SELECT A.TableA1.e1, A.TableA1.e2, B.TableB1.e1, B.TableB1.e2 FROM A.TableA1, B.TableB1 WHERE A.TableA1.e1 = B.TableB1.e1
They can much more complex join queries than above too.
--
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
[View Less]
14 years, 10 months