Welcome to Knowage Q&A, where you can ask questions and receive answers from other members of the community.
+2 votes
1 view

Hi,

I'm having problems setting up a postgresql data source as a JNDI connection. JDBC works fine. When I set up the same thing as JNDI, I can still create a Business Model on it, but the subsequent DataSets on those Business Models get no data. ( I have done a similar thing for a Oracle data source, which works ok.)

I have noticed that the .sbimodel definition of a Business Model (created with Meta Web) on my JDBC data source contains the string   <physicalModels name="model_name_mock" databaseName="PostgreSQL" databaseVersion="9.6.4" catalog="postgres" schema="test_dwh">, whereas the one defined on my JNDI data source lacks the schema information.

The name of the schema I want to query is not the same as the username and is called "test_dwh". My database name is "postgres".

My working JDBC connection has url="jdbc:postgresql://myserver:5432/postgres?currentSchema=test_dwh". For my JNDI connection, I put the same thing in my resource definition in server.xml, which I have propagated to all the context.xml files.

Should the Resource url in server.xml be like url="jdbc:postgresql://myserver:5432/postgres?currentSchema=test_dwh" or rather like url="jdbc:postgresql://myserver:5432/postgres" and what should the Multischema Attribute in the Data Source config window look like, if the schema in question is called "test_dwh"?

Thanks a lot!

Environment Knowage 6.0.0.CE on mysql-5.6.25-winx64 , Windows7 64bit, PostgreSQL 9.6.4, driver:postgresql-42.1.4.jar
in General Configuration by (2.6k points)
Same issue occurring with JDBC connections. Looking at some of the code, it appears that "public" is forced for the Business Model.
It's still not fixed. My postgre jdbc data source with multischema checked on yes only see public schema.

Hello mr.artemise. Did you find and fix problem with data source with multischema in Knowage?

1 Answer

0 votes
Hi, we will investigate this issue with PostgresSQL. I've opened a bug on the public tracker here: https://www.knowage-suite.com/jira/browse/KNOW-65

Thanks for reporting this problem.
by (11.6k points)
Dear

We've moved on GIThub, so we've created: https://github.com/KnowageLabs/Knowage-Server/issues/35

This problem is fixed on Knwoage 6.2

Best regards

Angelo
...