We have created the table CUSTOMER through zeppelin interface of VORA. Now I want to access this CUSTOMER via SAP LUMIRA . After starting the thrift server , we logged into JDBC connector command prompt using beeline as suggested in developer guide.
When I connected Lumira to JDBC connector , under CATALOG_VIEW , I can not find my table named CUSTOMER.
I tried to register the table CUSTOMER again under JDBC connector prompt but its gave error message.
Is it not possible to access same VORA table created using zeppelin interface in JDBC connection ?
Error Screenshot
Which version of Vora are you using? Connectivity to Lumira is only supported as of Vora 1.1.
If you use Ambari to manage the Vora installation you can check the version at 'Admin' -> 'Stacks and Versions'.
Its working now.... I passed attribute "namenoderul" in register table command , and table is visible under CATALOG _VIEW in lumira.
Related
I'm trying to do SQL query on redshift database without using JDBC. (I don't want to connect to JDBC to execute a SQL command in the redshift as shown in this link: https://docs.aws.amazon.com/redshift/latest/mgmt/connecting-in-code.html).
I'm connecting AmazonRedshift using redshift client builder
AmazonRedshift client = AmazonRedshiftClientBuilder.standard()
.withCredentials(awsCredentials).build();
Now I want to execute a SQL query using this client. I googled and found this example (https://docs.aws.amazon.com/redshift/latest/mgmt/managing-events-java.html) where they are using DescribeEventsRequest to get the events but I'm not sure whether this is the same API I should use to run SQL commands
Thanks in advance
The AWS SDK (AmazonRedshift client), can only be used to manage the Redshift cluster (create, delete, manage events, etc.) It cannot be used to execute queries.
To execute queries, you must use JDBC.
I have created a new Azure SQL Data Warehouse database on a new logical server from the backup of a Azure SQL Data Warehouse database on a different logical server (using the Azure portal). I created the LOGINs on the new MASTER database for the users that would connect to the new Azure SQL Data Warehouse database. The users were restored to the new Azure SQL Data Warehouse database as expected per:
SYS.DATABASE_PRINCIPALS
Now when I attempt to connect with those users, I receive an error:
Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : The instance of SQL Server you attempted to connect to does not support CTAIP..
We use sql-server authentication, running the following on both the original and new MASTER:
CREATE LOGIN
the_userID
with password = 'xxxxxxxxxxxxxxxxx'
;
GO
and the following pattern on the original ADW database:
CREATE USER [the_userID] FROM LOGIN [the_userID]
;
GO
Is there any solution other than dropping and reCREATEing the users in the new ADW database?
CTAIP error is a rather poorly worded error message indicating the login (in master) does not have a corresponding user in the DW.
In this case, you need to drop the existing user in the DW and re-create it for the login in master.
It doesn’t work automagically (yet) because we track the association using security identifiers (SID) not names and the new login in master has a new/unique SID. AAD logins and contained users (not currently supported in DW) don’t have this problem.
I have configured API Manager 2.0.0 & API Manager Analytics Pack to use MySQL databases.
For each server, there exists a WSO2AM_STATS_DB. I have given these differing names on my MySQL server. I have also pointed my datasources in master-datasources.xml(for APIM) & stats-datasources.xml(for Analytics) to the relevant databases.
I couldn't find any relevant schema(dbscripts) for these databases in their respective packs.
On running, the Analytics database is populated but the APIM database isn't and throws an exception. The Analytics database not only gets the schema but also the invocation details of my API.
I am unable to get the stats on my dashboard though.
Previously, I (unwittingly) configured the h2-repository stats database to be the same for both servers (due to the folder structure) and was able to get all the statistics on my dashboard in the publisher.
Other configurations I have tried :
On the MySQL Server, pointed it to the same database (the Analytics one with the schema) but with no results on my dashboard (after waiting for a while).
Both datasources (WSO2AM_STATS_DB) in 2 servers should be pointed to the same database. There are no database scripts for this. Tables are created automatically.
By default in both servers, Stats DB path comes like this. (note ../ part)
<url>jdbc:h2:../tmpStatDB/WSO2AM_STATS_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=60000;AUTO_SERVER=TRUE</url>
So if you extract both servers to the same directory as mentioned in this doc, both datasources will be pointing to the same database (inside tmpStatDB) like this.
/parent_dir
|__wso2am-2.0.0/
|__wso2am-analytics-2.0.0/
|__tmpStatDB/
So, what happens here is, wso2am-analytics writes stats data to shared database, then apim reads it and shows data on its databases.
My mysql server is on the cloud. I install the connector to connect mysql on Window 7 machine. Then I try to connect from Power BI to MySQL server. I give the IP address and database name, my root credential. Then I click on save. It gives me the following error.
DataSource.Error: MySQL: Unable to connect to any of the specified MySQL hosts.
Details:
Message=Unable to connect to any of the specified MySQL hosts.
ErrorCode=-2147467259
Then I try to connect from mysql workbench with the same credential from the same machine. I can connect, but I am not connecting from Excel Power BI.
I found that you need to install a special driver to get PowerBi to work with MySQL. The link to that driver is actually in the error message (but you can't click on it or select the text?).
mysql-connector-net-6.6.5.msi
I found the file here.
I have found this link which explains my issue perfectly. In short :
Exception throws when AM configured with BAM (MySql) access the statistics page in the publisher
My problem is exactly this issue.
Is there a solution for the version 1.6.0 ?
Try to drop all the virtual tables in hive using a hive script.
In this case drop table APIRequestSummaryData
https://docs.wso2.org/display/BAM240/Adding+and+Editing+Analytic+Scripts