Latest Denodo community answered questions 2024-11-29T10:44:31Z 2024-11-29T10:44:31Z

Version : 8 install update 2023/14/09 Hello, I added a "where condition" via the web interface in a join view: periodicite in 'QUOT','HEBDOS','FERIER'. Extract of SQL sentence in denodo is : WHERE t17.periodicite IN (?, ?, ?) With the parameters: [QUOT, HEBDOS, FERIE]. When I look at the execution plan on the source (SQLSERVER), I see an implicit conversion on the periodicite column: CONVERT_IMPLICIT(nvarchar(30), [Vente].[dbo].[TITRE].[periodicite] as [t17].[periodicite], 0) = [@P198] OR CONVERT_IMPLICIT(nvarchar(30), [Vente].[dbo].[TITRE].[periodicite] as [t17].[periodicite], 0) = [@P197] OR CONVERT_IMPLICIT(nvarchar(30), [Vente].[dbo].[TITRE].[periodicite] as [t17].[periodicite], 0) = [@P196] The column in the table is of type VARCHAR(30). The base view in denodo also contain VARCHAR(30) type. Why are the values specified in the WHERE condition typed as NVARCHAR(30)? Is it necessary to always perform a CAST when specifying an alphanumeric value in this field? Regards, Emmanuel ********************************************************** I find the solution in another case : The solution was to change the Data Source property "Allow literal as parameter" from Yes to No.

2024-11-29T10:44:31Z 2024-11-28T19:29:21Z 2024-11-28T19:29:21Z

Hello, I have a view with a nested column, but the fields inside it don't have descriptions, even though the source fields do. How can I ensure that the nested fields inherit the descriptions from the source? br

2024-11-28T19:29:21Z 2024-11-26T12:49:29Z 2024-11-26T12:49:29Z

I have JSON-over-HTTP datasource with EAV (Entity-attribute-value) model inside, like this one: https://pastebin.com/raw/XhHgR0VM ``` [ { "id": "cb879cb8-a310-11ef-ba83-bab0678cb5af", "number": "000000000001", "date": "2024-09-10T21:34:55", "template": "96fd7bb1-9bf8-11ef-ba83-bab0678cb5af", "author": "Admin", "fields": [ { "fieldName": "date", "fieldDescription": "", "fieldType": "date", "fieldValue": "2024-09-10T21:34:55" }, { "fieldName": "sex", "fieldDescription": "", "fieldType": "reference", "fieldValue": "Male" }, { "fieldName": "amount", "fieldDescription": "", "fieldType": "number", "fieldValue": "5" }, { "fieldName": "diagnosis", "fieldDescription": "", "fieldType": "reference", "fieldValue": "Dystrophy" }, { "fieldName": "house", "fieldDescription": "", "fieldType": "reference", "fieldValue": "RM-1-2" } ] } ] ``` I want to represent it like a table, like this: ``` date | sex | amount | diagnosis | etc 2024-09-10T21:34:55 | Male | 5 | Dystrophy | ... ``` What is the proper way to get it?

2024-11-26T12:49:29Z 2024-11-25T08:57:12Z 2024-11-25T08:57:12Z

Hi team, after configured by steps above, i have error message while start denodo. "Starting Denodo Virtual DataPort Server ... (press ENTER in case shell prompt was not automatically returned) Could not load Logmanager "org.apache.logging.log4j.jul.LogManager" java.lang.ClassNotFoundException: org.apache.logging.log4j.jul.LogManager at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)" port 8081 & other ports are up and denodo working fine. but http://XXXX:8081/metrics not able to visit. could you advise?

2024-11-25T08:57:12Z 2024-11-21T18:03:21Z 2024-11-21T18:03:21Z

Is there a way to set up a template in the Description field that ensures all descriptions follow the same format?

2024-11-21T18:03:21Z 2024-11-21T12:28:30Z 2024-11-21T12:28:30Z

Hello We are currently using the predefined stored procedure `GET_PUBLIC_VIEW_DEPENDENCIES` to get the direct dependencies between the public views only. We want to do the same for the COLUMNS, but there is no predefined stored procedure for the public columns dependencies. The only available is `COLUMN_DEPENDENCIES` stored procedure which return private views. Hence, Is there a stored procedure to do that? Or how to elemenate the dependency on the private views so that all the direct dependencies are public views?

2024-11-21T12:28:30Z 2024-11-21T05:47:56Z 2024-11-21T05:47:56Z

Hello, how to query using VSQL server host where Denono is running? In Oracle we can use the query SELECT SYS_CONTEXT ('USERENV', 'SERVER_HOST') FROM DUAL; Thanks

2024-11-21T05:47:56Z 2024-11-18T09:34:07Z 2024-11-18T09:34:07Z

Hi, I'm trying to create a soap web service and I'm using XML formatted in the test environment but everytime that I execute the datasource I got the following error "Unable to establish connection: Error retrieving data from 'https://xxxxxxxxxxxxxx'. HTTP error code: 403." If I checked the log says "Stream Output"... any idea how to solve this issue ? Thankfully, Olga

2024-11-18T09:34:07Z 2024-11-14T05:42:44Z 2024-11-14T05:42:44Z

Denodo Express 9.0 connected to the following southbound data sources - 1. Snowflake 2. Postgres 3. MySQL 4. SQLite3 Able to copy a table from the MySQL data source to the Postgres data source using create_remote_table() without any issues. But when attempting the same from Snowflake; basically from the Snowflake data source to the same Postgres data source, the following error is encountered - ERROR: java.sql.SQLException: Error executing query. Total time 7.03 seconds. QUERY [SELECTION] [ERROR] CREATE_REMOTE_TABLE [STORED_PROCEDURE] [ERROR] CREATE_REMOTE_TABLE [STORED PROCEDURE] [ERROR] Received exception with message 'Error executing VQL query. QUERY [VIRTUAL] [ERROR] QUERY [JDBC WRAPPER] [ERROR] QUERY [JDBC ROUTE] [ERROR] Received exception with message 'Cannot invoke "com.denodo.vdb.engine.thread.IWorker.stop(int)" because "this.worker" is null'' I know Denodo Express has some license-restricted limitations and thought maybe this was one of them but given the MySQL/Postgres create_remote_table() success I'm thinking it is likely something else but that error message is challenging. Java version (Express): version=17.0.12 Snowflake driver in Express: version=3.14.3 Postgres driver in Express: version=42.7.2 Queries against the Snowflake data source in Express work smoothly both through VQL Shell and Design Studio as well as with JDBC clients connected to Express. Same for the Postgres data source. Any thoughts as to what is going on?

2024-11-14T05:42:44Z 2024-11-13T15:44:27Z 2024-11-13T15:44:27Z

Our Denodo DEV identifier charset is set to Unicode. Our Denodo TEST\PROD are both set to Restricted. We use Denodo VCS for our promotion strategy. DEV views when promoted to TEST\PROD retain their Unicode query behavior (meaning to successfully query the field names must be in double quotes and are case sensitive) as opposed to adopting that of the host which is set to Restricted. I have found that if I edit the promoted view(s) in TEST\PROD and resave them, then and only then do they adopt the charset of the host which in this case happens to be Restricted. I have validated identifier charset settings at both the server and the vdb levels for each environment to ensure this is not playing a role.

2024-11-13T15:44:27Z