[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=12572612#comment-12572612 ] 

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

So your issue is actually with dependent joins then?  In that case the logic is working as expected, but the 700 value is too large.

Right now setting the max IN would require creating a subclass of SaleForceExecutionFactory and overriding the getMaxInCriteriaSize method.  It seems like we could reduce the default, make the max a configurable translator property, or both to avoid this issue.

> 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