[teiid-issues] [JBoss JIRA] Commented: (TEIID-1412) Teiid should take care of salesforce query limits by itself

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572592#comment-12572592 ] 

Steven Hawkins commented on TEIID-1412:
---------------------------------------

Teiid has a max IN criteria size of 700 set for the salesforce translator.  This issue could be treated as an enhancement to the engine to perform the splitting you're looking for based upon that value.  The logic is a better fit in the engine in any case since it already has facilities for this logic based upon dependent joins - however it will not be directly related to the exact length of the salesforce query.

> Teiid should take care of salesforce query limits by itself
> -----------------------------------------------------------
>
>                 Key: TEIID-1412
>                 URL: https://issues.jboss.org/browse/TEIID-1412
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Salesforce Connector
>    Affects Versions: 7.1.1, 7.2, 7.3
>         Environment: Teiid 7.1.1 on EAP 5.1 with CXF
>            Reporter: Wanja Pernath
>            Assignee: Steven Hawkins
>
> Salesforce has a query string limit of 10.000 chars. When Teiid is calculating and executing a query like this:
> SELECT Opportunity where AccountId in (a,b,c,d,e,f,g,h,i)
> It could extend the 10.000 chars limit of Salesforce. Right now teiid just stops with an Exception. 
> Expected behavior is to have teiid splitting up the condition into correct portions and to execute the above query n times to circumvent the limit:
> SELECT Opportunity where AccountId in (a, b, c);
> SELECT Opportunity where AccountId in (d, e, f);
> SELECT Opportunity where AccountId in (g, h, i);

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira