[JBoss JIRA] (TEIID-3193) Teiid not removing/setting the correct TCCL before calling getMetadata on translator
by Michael Farwell (JIRA)
Michael Farwell created TEIID-3193:
--------------------------------------
Summary: Teiid not removing/setting the correct TCCL before calling getMetadata on translator
Key: TEIID-3193
URL: https://issues.jboss.org/browse/TEIID-3193
Project: Teiid
Issue Type: Bug
Components: Common
Affects Versions: 8.8
Reporter: Michael Farwell
Assignee: Steven Hawkins
Fix For: 8.10
Ramesh helped me debug a class loading issue that I'm experiencing with a custom translator and asked me to open this ticket based on his findings. The forum link is specified below and contains all of the necessary information.
Ramesh's words: "OK, I believe the geoTools is using the TCCL to load the schema, thus the error. However, the error is on the Teiid side not correctly removing/setting the correct TCCL before we call "getMetadata" call on the translator. You can add JIRA for this we will fix it."
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3192?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3192:
---------------------------------------
Added the initial commit. This keeps our api version at 22, so I moved the force wsc back to 22 from 26 for consistency. From here we can look at adding additional config parameters as needed to replace whatever the cxf config could have been used for.
The dynamic metadata does look the same between the old and the new version - except for some of the native types, which are reported differently such as _boolean rather than boolean.
I confirmed querying against all tables (although two tables marked as queryable through the api are actually not at api version 22) and updates. The bulk update logic was changed to use a single job and add all batches to that job rather than serially processing - which should improve performance.
I was able to confirm that batching now works and there is a corresponding performance improvement even for moderately sized results. A sample with 9000 small result rows through CXF was taking approximately ~8 seconds, vs. ~4.5 seconds through the partner api.
> Migrate Salesforce connectivity to sf partner api jars
> ------------------------------------------------------
>
> Key: TEIID-3192
> URL: https://issues.jboss.org/browse/TEIID-3192
> Project: Teiid
> Issue Type: Component Upgrade
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3192?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-3192 at 10/31/14 11:29 AM:
------------------------------------------------------------------
A couple of issues I have also noticed:
Insert should not strip quotes from string values, and bulk insert cannot handle literal values - insert into foo (a, b) values (?, 1), single row insert doesn't handle timestamp formatting, join results also don't handle timestamp values in the child, and bulk insert returns a single int rather than individual codes.
was (Author: shawkins):
A couple of issues I have also noticed:
Insert should not strip quotes from string values, and bulk insert cannot handle literal values - insert into foo (a, b) values (?, 1), single row insert doesn't handle timestamp formatting, and join results also don't handle timestamp values in the child.
> Migrate Salesforce connectivity to sf partner api jars
> ------------------------------------------------------
>
> Key: TEIID-3192
> URL: https://issues.jboss.org/browse/TEIID-3192
> Project: Teiid
> Issue Type: Component Upgrade
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3192?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3192:
---------------------------------------
A couple of issues I have also noticed:
Insert should not strip quotes from string values, and bulk insert cannot handle literal values - insert into foo (a, b) values (?, 1), single row insert doesn't handle timestamp formatting, and join results also don't handle timestamp values in the child.
> Migrate Salesforce connectivity to sf partner api jars
> ------------------------------------------------------
>
> Key: TEIID-3192
> URL: https://issues.jboss.org/browse/TEIID-3192
> Project: Teiid
> Issue Type: Component Upgrade
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3192?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3192:
---------------------------------------
The initial target of the migration will be the version 22 of the api. We can look changing our supported version with a different issue.
> Migrate Salesforce connectivity to sf partner api jars
> ------------------------------------------------------
>
> Key: TEIID-3192
> URL: https://issues.jboss.org/browse/TEIID-3192
> Project: Teiid
> Issue Type: Component Upgrade
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (TEIID-3191) Teiid global temporary table error with first invocation
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3191?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3191.
-----------------------------------
Fix Version/s: 8.7.1
8.9
Resolution: Done
Corrected the metadata check for the pk, which assumed a traditional temp table rather than the initial metadata entry.
> Teiid global temporary table error with first invocation
> --------------------------------------------------------
>
> Key: TEIID-3191
> URL: https://issues.jboss.org/browse/TEIID-3191
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
> Attachments: nativeSQL.vdb
>
>
> When working with global temporary table in teiid an error occurs while accessing the temp table for the first time.
> Error: org.teiid.metadata.Column cannot be cast to org.teiid.query.metadata.TempMetadataID
> All the following invocations of the global temporary table run fine.
> Global temporary table is defined through Teiid designer within my vdb.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3192:
-------------------------------------
Summary: Migrate Salesforce connectivity to sf partner api jars
Key: TEIID-3192
URL: https://issues.jboss.org/browse/TEIID-3192
Project: Teiid
Issue Type: Component Upgrade
Components: Salesforce Connector
Reporter: Steven Hawkins
Assignee: Mark Drilling
Fix For: 8.10
There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month