[JBoss JIRA] (TEIID-5080) Teiid startup jdk9
by Lukáš Svačina (JIRA)
Lukáš Svačina created TEIID-5080:
------------------------------------
Summary: Teiid startup jdk9
Key: TEIID-5080
URL: https://issues.jboss.org/browse/TEIID-5080
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 9.3.3
Reporter: Lukáš Svačina
Assignee: Steven Hawkins
Attachments: stderr.txt, stdout.txt
Starting teiid 9.3.3 (with WildFly included) using java sdk 9 ends with several errors. See attached logs stdout/stderr.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIID-5074) Support a way provide SEQUENCE in TeiidDialect
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5074?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5074:
-------------------------------------
Can you log an issue for generating the SEQUENCE DDL in source models where it is supported?
> Support a way provide SEQUENCE in TeiidDialect
> ----------------------------------------------
>
> Key: TEIID-5074
> URL: https://issues.jboss.org/browse/TEIID-5074
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific of way to insert a layer in Teiid to accomplish this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIID-5079) Salesforce issues
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5079:
-------------------------------------
Summary: Salesforce issues
Key: TEIID-5079
URL: https://issues.jboss.org/browse/TEIID-5079
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0
In looking into other issue two small salesforce issues cropped up:
1. setting modelAuditFields requires using the translator property - the import property is ignored. This also doesn't seem to be documented.
2. Creating a join where fields are omitted from the child result in a malformed query:
SELECT Account.Name FROM Account LEFT OUTER JOIN Contact ON Account.Id = Contact.AccountId
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIID-5074) Support a way provide SEQUENCE in TeiidDialect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5074?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5074:
---------------------------------------
Yes, we do with TEIID-3270. But I'm not quite sure what situation that would be needed under.
> Support a way provide SEQUENCE in TeiidDialect
> ----------------------------------------------
>
> Key: TEIID-5074
> URL: https://issues.jboss.org/browse/TEIID-5074
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific of way to insert a layer in Teiid to accomplish this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5077:
---------------------------------------
> If the column in source model is modelled as string, shouldn't the value be actually retreived as string, without the TONUMBER function?
Only if you are querying the source table directly. If you query the view and it adds a conversion that is supported by the source, then we'll push it down.
Of course if we feel this is something that we want to compensate completely for, then we would need to change the import type mapping for long/biginteger to string and remove support for the pushdown of conversion to long/biginteger.
This also calls into question the support of bigdecimal as the issue implies the only numeric type that is properly supported is double - but bigdecimal expects fixed and possibly arbitrary precision.
> Couchbase strange behaviour for long numbers
> --------------------------------------------
>
> Key: TEIID-5077
> URL: https://issues.jboss.org/browse/TEIID-5077
> Project: Teiid
> Issue Type: Bug
> Components: Documentation, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Critical
>
> There is a strange limitation for storing large numbers (e.g. modelled as long) in Couchbase.
> https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numb...
> The same behaviour with value: 28341791043587382
> which is being stored and retreived as: 28341791043587384
> I feel we need to document this behaviour and provide hints how to overcome it. (Modelling of the column as string on Couchbase's side and defining a view).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIID-5074) Support a way provide SEQUENCE in TeiidDialect
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5074?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5074:
-------------------------------------
The reason I used the Procedure over a function is so that I can define the contents of the procedure using SQL block. Do we allow functions with SQL statements now?
> Support a way provide SEQUENCE in TeiidDialect
> ----------------------------------------------
>
> Key: TEIID-5074
> URL: https://issues.jboss.org/browse/TEIID-5074
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific of way to insert a layer in Teiid to accomplish this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5077:
------------------------------------
bq. has it been confirmed that this directly affects our Couchbase usage
Yes, I've hit the issue with the number provided in description.
bq. Also does the proposed workaround actually work?
You're right, it does not work.
If the column in source model is modelled as string, shouldn't the value be actually retreived as string, without the TONUMBER function?
> Couchbase strange behaviour for long numbers
> --------------------------------------------
>
> Key: TEIID-5077
> URL: https://issues.jboss.org/browse/TEIID-5077
> Project: Teiid
> Issue Type: Bug
> Components: Documentation, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Critical
>
> There is a strange limitation for storing large numbers (e.g. modelled as long) in Couchbase.
> https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numb...
> The same behaviour with value: 28341791043587382
> which is being stored and retreived as: 28341791043587384
> I feel we need to document this behaviour and provide hints how to overcome it. (Modelling of the column as string on Couchbase's side and defining a view).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years