You can translate the question and the replies:

Dynamic Parameter in CONTEXT is not actually passing through Denodo

Hi , I am in the use case where VQL shell applies fectch limit(Delegation to source is set YES in Datasource config) and gets result in 10-20 secs for any base view, while the same connection I am using in DBeaver(has its own limit of 200 records)-->Denodo-->Source, and DBeaver sends a query which has applied the limit in CONTAXT clause which comes after a JDBC query, and that query takes so long to execute, so, it means the CONTEXT is not working or JDBC limit applies througn Any tool to Denodo is not working? Please help.! Thanks.
Denodo Dbeaver Context keyword
user
22-12-2023 13:10:04 -0500
code

1 Answer

Hi, I tried to recreate a similar scenario by creating a connection in Dbeaver with Denodo. For instance, if I have a view named ‘sample’ with limit set as 10 in Denodo, as in the the below query: ``` SELECT * FROM sample LIMIT 10 CONTEXT ('i18n'='us_pst') ``` I got the results within a **few milliseconds(ms)** on executing this view. However, if I execute the same query in Dbeaver with Denodo as source, then I get the results with a few milliseconds delay, as the query fetches the results from source. If the difference in execution time is so large, the possible reasons may be due to network latency, conditions such as region of instances, resources or might be due to more traffic in source. I would check the [Execution Trace](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/creating_derived_views/querying_views/execution_trace_of_a_statement) of the query to analyze the reason for the delay. Hope this helps!
Denodo Team
26-12-2023 07:46:27 -0500
code
You must sign in to add an answer. If you do not have an account, you can register here