Postgres shema settings

PeterLalor shared this question 2 years ago
Answered

Hi I have a Postgres db with multiple shemas. Im having problems setting up a connection and then accessing the data in the tables in any of the schemas. It seems that YF isnt passing the shema name into the SQL it generates (regardless of what I set in the connection settings for the db).


I dont have any control over the schemas - they are created by another application so I need to be able to point YF at the various schemas.


Is this is a known issue?

Comments (10)

photo
1

Hi Peter,


Thanks for sending this in. We did have a known issue a couple of builds ago that sounds a lot like what you're experiencing. Specifically, it was when a user wanted to create a single table view and had multiple schemas. The schema names did not get saved, regardless of having that connection option being checked. This caused errors when trying to build views, as Yellowfin would indiscriminately grab data from the wrong schemas.


I have a couple quick questions:

  • What type of database are you pulling from? (Postgres, Oracle, MySQL, etc.)
  • Are you trying to create single table views?
  • What is you current build and version of Yellowfin? This can be found in the System Information section of the Admin Console in Yellowfin.


The issue described above was fixed in the October build of Yellowfin, so if you are running an older builder, a simple upgrade should be all that is need to fix this. Hopefully this is some good news! However, if you are on the most current build please let me know so that we can go after this further.


Thanks,

-Conner

photo
1

Hi Conner,

database is Postgres, YF version is 7.2 build 20160524.  We are running a hosted YF instance from AWS.  Not sure how this is upgraded - I assumed it would be automatically on the latest build?

Yes I was setting up a single table view - but I can try a multi table view.

Peter

Regards,

Peter Lalor

CEO

phone  0401 716 194

email  plalor@moneybrilliant.com.au

web  www.moneybrilliant.com.au

logo_email

Note: The information transmitted in this message is intended only for the person or entity to whom (or which) it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

On 10 November 2016 at 10:40, Yellowfin Support Team wrote:

photo
1

Hi Conor, Im pretty sure there is a bug in the YF version we are using. I dont seem to have any control over which schema tables are being selected from when I create universes which makes it unusable. How do we get our instance of YF upgrded to the latest version?

photo
1

Hi Peter,


Thanks for the follow up with that information. It definitely sounds to me like you're experiencing that known issue that I mentioned above. An upgrade should solve this and get you going properly. Yellowfin does not upgrade itself automatically. Getting the latest build pushed out to our 'default' hosted instances is something that is currently in progress. (This won't affect your instance, the change will only be experienced by people who spin up brand new ones.)


We have a quick guide on how to upgrade your AWS instance to the latest build, which can be found here:

http://community.yellowfin.bi/knowledge-base/article/how-to-update-yellowfin-on-linux-and-the-aws-marketplace-instance


Please let me know if you have any questions about the upgrade process, or if there is anything else that we can do for you from Support.


Thanks,

-Conner

photo
1

Hi Conor,


we will do the upgrade some time next week. Thanks for your help

photo
1

Peter,


Sounds good, keep us posted!


Thanks,

-Conner

photo
1

Hi Conor,


we would like to do this upgrade to our hosted AWS instance. Can you point me to the latest YF upgrade file please?

photo
1

Hi Peter,


Of course, the latest 7.2 build can be found here:


http://files.yellowfin.bi/downloads/7.2/yellowfin-20161024-update.jar


Please us know how the upgrade goes, or if you have any questions on the process.


Thanks,

Conner

photo
1

Hi Conor,

upgrade done.  Went smoothly.  Im yet to check the bug we had but will advise shortly.

Regards,

Peter Lalor

CEO

phone  0401 716 194

email  plalor@moneybrilliant.com.au

web  www.moneybrilliant.com.au

logo_email

Note: The information transmitted in this message is intended only for the person or entity to whom (or which) it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

On 22 November 2016 at 10:40, Yellowfin Support Team wrote:

photo
1

Peter,


Excellent, thanks for passing along the good news! Let us know how your testing goes, or if you have any other questions. The change logs for the release you installed can be found at the following link if you haven't already taken a look:

http://community.yellowfin.bi/knowledge-base/article/build-7-2-november-2016


Best,

-Conner