[JBoss JIRA] (TEIID-4456) Enable the abiltiy to specify all the message descriptors when using protobuf configuration
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ]
Van Halbert reassigned TEIID-4456:
----------------------------------
Assignee: Van Halbert (was: Steven Hawkins)
> Enable the abiltiy to specify all the message descriptors when using protobuf configuration
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-4456
> URL: https://issues.jboss.org/browse/TEIID-4456
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 9.2
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Change configuration to enable the specification of all the protobuf descriptors to use.
> Currently, only the root protobuf descriptor is configured. Example:
> {code}
> <config-property name="MessageDescriptor">
> bigdata.DataEntity
> </config-property>
> {code}
> Because of this, the children message descriptors have to be defined within the parent message descriptor. If all message descriptors can be specified, then children message descriptors can be defined at the top level and shared.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIID-4455) Impala Translator - Change planning step for from_unixtime() pushdown
by Don Krapohl (JIRA)
Don Krapohl created TEIID-4455:
----------------------------------
Summary: Impala Translator - Change planning step for from_unixtime() pushdown
Key: TEIID-4455
URL: https://issues.jboss.org/browse/TEIID-4455
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector
Affects Versions: 9.0.4, 8.13.x
Reporter: Don Krapohl
Assignee: Steven Hawkins
Priority: Minor
Impala and Teiid both have from_unixtime() functions and per the forum reference the mapping to timestampadd() appears to come before the test for pushdown support of the impala native function.
As a query request we require the impala from_unixtime() function be executed instead of the Teiid-native version.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIID-4454) Close session called with null session id
by Wouter de Vaal (JIRA)
Wouter de Vaal created TEIID-4454:
-------------------------------------
Summary: Close session called with null session id
Key: TEIID-4454
URL: https://issues.jboss.org/browse/TEIID-4454
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.0.4
Reporter: Wouter de Vaal
Assignee: Steven Hawkins
Priority: Minor
When connecting locally via a JNDI resource to a vdb, we see in our audit log that an extra closeSession is logged with a null session id, just before a new session is created.
This is probably because the class LocalServerConnection.authenticate calls logoff
Logoff will execute a logoff command with swallowing all exceptions:
try {
//make a best effort to send the logoff
Future<?> writeFuture = this.getService(ILogon.class).logoff();
if (writeFuture != null) {
writeFuture.get(5000, TimeUnit.MILLISECONDS);
}
} catch (Exception e) {
//ignore
}
And this method will call closeSession without even checking if there is a session to logoff:
try {
this.service.closeSession(workContext.getSessionId());
} finally {
this.updateDQPContext(new SessionMetadata());
}
So fix should probably be adding an if statement to LogofImpl.logoff
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIID-4351) JDG: Does not support 1-to-1 relationship
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4351?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4351.
-----------------------------------
Resolution: Done
Merged the pull request. Thanks Van.
> JDG: Does not support 1-to-1 relationship
> -----------------------------------------
>
> Key: TEIID-4351
> URL: https://issues.jboss.org/browse/TEIID-4351
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.x, 8.7.6
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 9.1
>
>
> When the primary object has a defined 1-to-1 relationship, the internal relationship isn't generating a second table by the metadata processor, even though its defined in the protobuf definition file and the marshallers. And when the second table is manually built, and then tried to preview, the server is throwing a methodNotFound exception, because its looking back on the primary object for the method, not the internal object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIID-3439) Add support for aliases with .
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3439?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3439:
----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Add support for aliases with .
> ------------------------------
>
> Key: TEIID-3439
> URL: https://issues.jboss.org/browse/TEIID-3439
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We currently don't allow column or table aliases to contain '.'. This is allowable given a quoted identifier is used. However an early design decision of metamatrix was to relax the rules of naming so that queries against the engine could use quoting (on not) similar to whatever was expected by a given database rather than the engine structure. A lot of resolving and parsing logic will need to change unfortunately to fix this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months