[JBoss JIRA] (TEIID-2248) Implement Salesforce Bulk API for inserts/updates to Salesforce Connector
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2248?page=com.atlassian.jira.plugin... ]
Van Halbert moved PRODMGT-250 to TEIID-2248:
--------------------------------------------
Project: Teiid (was: Product Management)
Key: TEIID-2248 (was: PRODMGT-250)
Workflow: jira (was: JBoss Platforms RFE Workflow v2)
Component/s: Salesforce Connector
(was: Enterprise SOA Platform (SOA-P))
(was: Metamatrix)
> Implement Salesforce Bulk API for inserts/updates to Salesforce Connector
> -------------------------------------------------------------------------
>
> Key: TEIID-2248
> URL: https://issues.jboss.org/browse/TEIID-2248
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Marc Shirley
> Assignee: Ken Johnson
>
> Wish to utilize the Salesforce Bulk API for large inserts/updates. The specific use case was for writing/updating a million record table back up to their Salesforce instance. This will improve performance for large writes to the Salesforce instance.
--
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, 2 months
[JBoss JIRA] (TEIID-2202) Incorrect aggregate rewriting on DB2/AS400 using UDF
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created TEIID-2202:
-------------------------------------
Summary: Incorrect aggregate rewriting on DB2/AS400 using UDF
Key: TEIID-2202
URL: https://issues.jboss.org/browse/TEIID-2202
Project: Teiid
Issue Type: Bug
Components: JDBC Connector, Query Engine
Affects Versions: 7.7.1
Reporter: Hisanobu Okuda
Assignee: Steven Hawkins
When I run the following query, the count(*) in the middle inline view, gets rewritten as a sum and a count in the most inner inline view. This has something to do with my the parseDate_ UDF. This is a change from EDS 5.2 where it worked correctly. I've included logs from both for contrast.
Query:
SELECT
examiner,
exam_date,
exam_date_code,
num_claims,
company_id,
1 AS enterprise_id
FROM
(
SELECT
examiner,
parseDate_(exam_date_code) AS exam_date,
exam_date_code,
company_id,
COUNT(*) AS num_claims
FROM
(
SELECT
CASE
WHEN (ME4.ADJUSR <> ' ')
AND (ME4.APRUSR <> ' ')
THEN
CASE
WHEN ME4.APRDAT >= ME4.ADJDAT
THEN ME4.APRUSR
ELSE ME4.ADJUSR
END
WHEN (ME4.APRUSR <> ' ')
AND (ME4.ADJUSR = ' ')
THEN ME4.APRUSR
WHEN (ME4.APRUSR = ' ')
AND (ME4.ADJUSR <> ' ')
THEN ME4.ADJUSR
ELSE MED.ADJUSR
END AS examiner,
CASE
WHEN (ME4.ADJUSR <> ' ')
AND (ME4.APRUSR <> ' ')
THEN
CASE
WHEN ME4.APRDAT >= ME4.ADJDAT
THEN ME4.APRDAT
ELSE ME4.ADJDAT
END
WHEN (ME4.APRUSR <> ' ')
AND (ME4.ADJUSR = ' ')
THEN ME4.APRDAT
WHEN (ME4.APRUSR = ' ')
AND (ME4.ADJUSR <> ' ')
THEN ME4.ADJDAT
ELSE MED.LSTCHG
END AS exam_date_code,
CONVERT(MED.COMPNO, INTEGER) AS company_id
FROM
FCC.MEDMAS AS MED
INNER JOIN
FCC.ME4MAS AS ME4
ON
MED.BRANCD = ME4.BRANCD
AND MED.BATDAT = ME4.BATDAT
AND MED.BATSEQ = ME4.BATSEQ
AND MED.SEQNUM = ME4.SEQNUM
WHERE
(MED.SYSDAT >= curdate_('-11 months 1st day'))
AND (MED.LINENO = 1)
AND (MED.STATCD <> 'O')
AND ((ME4.ADJUSR <> ' ')
OR (ME4.APRUSR <> ' ')
OR (MED.ADJUSR <> ' '))) AS Event
GROUP BY
Event.examiner,
Event.exam_date_code,
Event.company_id) AS Count_By_Examiner_ID
--
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, 2 months
[JBoss JIRA] (TEIID-2177) Expand native-query support
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2177:
-------------------------------------
Summary: Expand native-query support
Key: TEIID-2177
URL: https://issues.jboss.org/browse/TEIID-2177
Project: Teiid
Issue Type: Sub-task
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
The native-query extension metadata is currently understood only by jdbc. We should add support in olap, ldap, salesforce, 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, 2 months
[JBoss JIRA] (TEIID-2237) jdbc native query issues
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2237:
-------------------------------------
Summary: jdbc native query issues
Key: TEIID-2237
URL: https://issues.jboss.org/browse/TEIID-2237
Project: Teiid
Issue Type: Feature Request
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
A non-prepared procedure only works if the procedure has no parameters. It should be allowed to work even with parameters through literal substitution.
Also the parsing loop incorrectly increments the parsing position after a match. This means that the character after a positional reference is lost. The workaround for typical scenarios would be to use extra whitespace. i.e.
instead of "select * from tbl where x = $1 and y = $2",
use "select * from tbl where x = $1 and y = $2"
--
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, 2 months
[JBoss JIRA] (TEIID-2176) Expose invoke procedures for querable sources
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2176:
-------------------------------------
Summary: Expose invoke procedures for querable sources
Key: TEIID-2176
URL: https://issues.jboss.org/browse/TEIID-2176
Project: Teiid
Issue Type: Sub-task
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
We should add procedures similar to invokeMDX that allow native query execution. This would compliment the canned native-query feature to allow fully dynamic query execution.
TEIID-2111 will also provide vararg capabilities should we need it.
--
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, 2 months