[
https://issues.jboss.org/browse/TEIIDSB-135?page=com.atlassian.jira.plugi...
]
Steven Hawkins commented on TEIIDSB-135:
----------------------------------------
But can you explain, please. For make $top work we need in odata
requests always set $orderby?
No, you do not need an explicit order by. The entities are always implicit ordered by id,
so for a top an order by is effectively being pushed down already. Then by default the
salesforce translator is indicating that order by is not supported, so the sorting is
performed in the engine. As a workaround there is a translator property, supportsOrderBy,
that can be set to true in the vdb or in your application properties.
top in odata query is not working
---------------------------------
Key: TEIIDSB-135
URL:
https://issues.jboss.org/browse/TEIIDSB-135
Project: Teiid Spring Boot
Issue Type: Bug
Components: OData
Affects Versions: 1.2.0
Environment: teiid-spring-boot+spring-odata teiid+spring-data-salesforce
Reporter: Renat Eskenin
Priority: Major
When we call simple request as
salesforce-odata-facade/odata/salesforce/Product_License__c?$top=1&$select=Id
request processing time is 1min. But this request processing by simple SOAP SOQL request
is ~150ms.
I think this do because teiid select all objects by ignoring top in request.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)