[JBoss JIRA] (TEIID-2483) Error trying to connect to Teiid using 8.3 code in Designer against an 8.4 server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2483?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2483.
---------------------------------
> Error trying to connect to Teiid using 8.3 code in Designer against an 8.4 server
> ---------------------------------------------------------------------------------
>
> Key: TEIID-2483
> URL: https://issues.jboss.org/browse/TEIID-2483
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 8.4
>
>
> This is the stacktrace I got when testing the connection to Van's new cluster at
> redhat-stl-eng3.usersys.redhat.com.
> org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException
> at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433)
> at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1)
> at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658)
> at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575)
> at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136)
> at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29)
> at
> org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58)
> <snip>
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> Caused by: java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124)
> at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194)
> at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349)
> at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430)
> ... 48 more
--
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, 4 months
[JBoss JIRA] (TEIID-2563) assignDataSource issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2563?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2563.
---------------------------------
> assignDataSource issues
> -----------------------
>
> Key: TEIID-2563
> URL: https://issues.jboss.org/browse/TEIID-2563
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> The assignDataSource admin operation has several issues
> - it uses different logic to create translator instances (which means that it cannot newly create delegating transaltors)
> - it adds new ConnectorManagers to the repository before they are valid (may have the wrong ExecutionFactory)
> - if the datasource is changes, the translator will stay same regardless of if it is being changed
--
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, 4 months
[JBoss JIRA] (TEIID-2659) A domain member server cannot list translators
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2659?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2659.
---------------------------------
> A domain member server cannot list translators
> ----------------------------------------------
>
> Key: TEIID-2659
> URL: https://issues.jboss.org/browse/TEIID-2659
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: 8.4.1
>
>
> Using the teiid client and calling 'admin.getTranslators()' fails to return any translators on a domain-member server. (this partially succeeds on the domain master)
> The request does not throw an exception but its outcome fails with the following result:
> {code}
> "outcome" => "failed",
> "failure-description" => "JBAS010849: Operation list-translators for address [
> (\"profile\" => \"ha\"),
> (\"subsystem\" => \"teiid\")
> ] can only be handled by the master Domain Controller; this host is not the master Domain Controller",
> "rolled-back" => true
> {code}
--
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, 4 months
[JBoss JIRA] (TEIID-2660) OData procedure issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2660?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2660.
---------------------------------
> OData procedure issues
> ----------------------
>
> Key: TEIID-2660
> URL: https://issues.jboss.org/browse/TEIID-2660
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4.1, 8.5
>
>
> Calling a procedure through Teiid's odata interface has several issues. First is that joda time values are passed directly - which the runtime will not be able to convert to analogous Teiid time types. Ultimately this appears as a classcastexception, which is due to logic in the joda time AbstractPartial.compareTo method (which may be reported with an erroneous message and seems odd in general, but is their way of saying the comparison is invalid).
> Another is that the logic assumes that the url will be called with the positional ordering of the parameters preserved. We should use named parameters instead.
--
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, 4 months
[JBoss JIRA] (TEIID-2569) Inefficient Outer Join compensation when translator restricted on KEY based joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2569?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2569.
---------------------------------
> Inefficient Outer Join compensation when translator restricted on KEY based joins
> ---------------------------------------------------------------------------------
>
> Key: TEIID-2569
> URL: https://issues.jboss.org/browse/TEIID-2569
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> When the following capabilities are set on ExecutionFactory
> {code}
> setSupportsOuterJoins(true);
> setSupportedJoinCriteria(SupportedJoinCriteria.KEY);
> {code}
> A three table JOIN like
> {code}
> select G1.e1, G2.e1, G3.e1 from G1, G2, G3 where G1.e1=G2.e2 and G2.e2 = G3.e3
> {code}
> gets pushed to translator as two separate queries like
> {code}
> SELECT G3.e3 AS c_0, G3.e1 AS c_1 FROM G3 ORDER BY c_0
> SELECT G2.e2 AS c_0, G1.e1 AS c_1, G2.e1 AS c_2 FROM G1 LEFT OUTER JOIN G2 ON G1.e1 = G2.e2 WHERE G2.e2 IS NOT NULL ORDER BY c_0
> {code}
> instead of of one query which should be like
> {code}
> SELECT G1.e1, G2.e1, G3.e1 FROM G1 INNER JOIN G2 ON G1.e1 = G2.e2 INNER JOIN G3 ON G2.e2 = G3.e3
> {code}
> When the key restriction is removed, it works fine, which should be un-related.
--
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, 4 months
[JBoss JIRA] (TEIID-2408) statistics of teiid query queuing information
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2408?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2408.
---------------------------------
> statistics of teiid query queuing information
> ---------------------------------------------
>
> Key: TEIID-2408
> URL: https://issues.jboss.org/browse/TEIID-2408
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi
> Affects Versions: 8.2
> Reporter: Jack Ma
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> At currently version of teiid, there is no teiid queuing information available from either teiid api or log or jmx, like how many query plans are still in the waiting queue, how many are in the active queue etc. .Thinking those queuing information is pretty critical for performance tuning up,
> Based on the Ramesh's suggestion, creating this request for probably a statistics max water mark in the waiting queue, and average time spent in waiting queue etc.
--
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, 4 months
[JBoss JIRA] (TEIID-2522) Let Extract(<Oracle Date field>) extract time components
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2522?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2522.
---------------------------------
> Let Extract(<Oracle Date field>) extract time components
> --------------------------------------------------------
>
> Key: TEIID-2522
> URL: https://issues.jboss.org/browse/TEIID-2522
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Alex K.
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.5
>
>
> According to the Oracle's docs:
>
> "The DATE datatype stores point-in-time values (dates and times) in a table. The DATE datatype stores the year (including the century), the month, the day, the hours, the minutes, and the seconds (after midnight)."
>
> I expect to be able to extract the time parts from a date field, but when I am trying to extract the hour from an oracle's date field like:
>
> {code:sql}
> SELECT EXTRACT(HOUR FROM a.modifieddate)
> FROM oracle_db.salestaxrate a
> WHERE a.salestaxrateid = 1
> {code}
>
> and get a TEIID30504 exception. When I look deeper in Teiid's log, i see the following Oracle's exception:
>
> Caused by: java.sql.SQLException: Remote java.sql.SQLException: ORA-30076: invalid extract field for extract source
> That is an odd Oracle limitation - http://docs.oracle.com/cd/B28359_01/server.111/b28286/functions052.htm
>
> "If HOUR, MINUTE, or SECOND is requested, then expr must evaluate to an expression of datatype TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITH LOCAL TIME ZONE, or INTERVAL DAY TO SECOND. DATE is not valid here, because Oracle Database treats it as ANSI DATE datatype, which has no time fields."
> *please enable extracting of time components from oracle's Date Fields* despite the Oracle's limitation
--
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, 4 months
[JBoss JIRA] (TEIID-2553) Partial insert statements being submitted with incorrect default values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2553?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2553.
---------------------------------
> Partial insert statements being submitted with incorrect default values
> -----------------------------------------------------------------------
>
> Key: TEIID-2553
> URL: https://issues.jboss.org/browse/TEIID-2553
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Bobby Diaz
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4.1, 8.5
>
>
> InsertResolver is causing incorrect default values to be returned by the ResolverUtil due to the wrong element symbol being sent to the ResolverUtil.getDefault() method. In the code below, taken from InsertResolver.getVariableValues(), I believe the first two rows inside the if statement should be reversed so that next.clone() is used to determine the default value rather than the varSymbol whose type has been changed to BOOLEAN.
> Collection<ElementSymbol> insertElmnts = ResolverUtil.resolveElementsInGroup(insert.getGroup(), metadata);
> insertElmnts.removeAll(insert.getVariables());
> Iterator<ElementSymbol> defaultIter = insertElmnts.iterator();
> while(defaultIter.hasNext()) {
> ElementSymbol next = defaultIter.next();
> ElementSymbol varSymbol = next.clone();
> varSymbol.getGroupSymbol().setName(ProcedureReservedWords.CHANGING);
> varSymbol.setType(DataTypeManager.DefaultDataClasses.BOOLEAN);
> result.put(varSymbol, new Constant(Boolean.FALSE));
> if (!changingOnly) {
> Expression value = ResolverUtil.getDefault(varSymbol, metadata);
> varSymbol = next.clone();
> varSymbol.getGroupSymbol().setName(SQLConstants.Reserved.NEW);
> result.put(varSymbol, value);
> }
> }
--
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, 4 months