You can translate the question and the replies:

Analytic Functions at the Denodo engine level

My team has been running into quite a bit of issues with analytic functions when joining across data sources. We have experimented and worked with data movement to resolve some of these issues. However, reporting packages (like Looker) do not have the ability to dynamically build VQL statements with the DATAMOVEMENT clause at the end of the VQL statement. Can someone explain why analytic functions must be pushed down to the data source and can't be executed at the Denodo engine level? Is there a plan to make analytic functions available at the Denodo engine level in the future? Thanks in advance.
user
24-02-2023 12:48:49 -0500
code

1 Answer

Hi! Currently, Virtual DataPort can delegate analytic functions but cannot execute them. There is an internal enhancement to support this feature in the future. If a database doesn’t support the analytic function that is included in the query, the query will fail. You can use DATAMOVEMENT or a full cache on the view in order to be able to delegate the analytical function as described in the section [Workaround to Execute Analytic Functions](https://community.denodo.com/docs/html/browse/8.0/en/vdp/vql/functions/analytic_functions/analytic_functions#workaround-to-execute-analytic-functions) I hope this helps!
Denodo Team
27-02-2023 06:28:30 -0500
code
You must sign in to add an answer. If you do not have an account, you can register here