Does infobright support data movement via Sqoop. I tried using mysql connector jdbc jar - 5.1.31. But I get access denied on the user. Same user I am able to login via dbeaver.
If it is possible can someone share the connection URL or any specific driver required with infobright. A sample sqoop job would be great.
Related
I am using the MSSQL database for WSO2 API manager 3.2.0 and want to use analytics. When I changed the database to MSSQL, this error appeared. How can I solve this problem?
You need to add the MSSQL JDBC driver to the <API-M_ANALYTICS_HOME>/lib directory to use MSSQL as the external database for Analytics. I have tried with mssql-jdbc version 8.2.2.jre8. Since mssql-jdbc depends on OSGi Service JDBC you will need to add that jar as well to the <API-M_ANALYTICS_HOME>/lib directory. You may use the following links to download the jars,
OSGi Service JDBC - https://mvnrepository.com/artifact/org.osgi/org.osgi.service.jdbc/1.0.1
Microsoft JDBC Driver For SQL Server - https://mvnrepository.com/artifact/com.microsoft.sqlserver/mssql-jdbc/8.2.2.jre8
If you still face issues after adding the above jars, please add the complete stack trace related to the error. You can find the logs in the carbon.log file located at <API-M_ANALYTICS_HOME>/wso2/worker/logs.
I am connecting to a SQL Serverless endpoint located in my Azure Synapse Account for my PowerBI Datasets. I am reading a SQL view that is composed of some parquet files in my data lake.
I am able to connect to the data fine when using PowerBI Desktop since it is using my Active Directory account. But now that I have the report published to a PowerBI Workspace online for other users in my organization I want to have it refresh the dataset daily without having to publish it myself.
Using the online refresh settings I am able to connect to SQL just fine using basic authentication (username/password) but it looks like when PowerBI renders the view it is also checking the credentials for the underlying datalake data which it does not have access to:
Microsoft SQL: Cannot find the CREDENTIAL 'https://mydatalake.dfs.core.windows.net/parquet/**', because it does not exist or you do not have permission. Could not use view or function 'dbo.MyView' because of binding errors.
What is the best way for me to give my PowerBI Workspace permissions to read this view (along with underlying datalake files)?
I'm also puzzled that in PowerBI Workspace I had options to schedule this data set but after a few failed attempts it now states:
You can't schedule refresh for this dataset because the following data sources currently don't support refresh:
And there is nothing after the ":" so now it appears I cannot attempt to connect anymore.
I have the PowerBI Workspace set as a linked service but that does not seem to help since I believe that is only for Synapse to use to connect to the workspace and not the other way.
I was toying with the idea of having Synapse copy the view data to a SQL database outside of Synapse so it can be shared more easily - but my preference would be to avoid this extra layer.
I have mysql database. When i trying to configure DataSource, im getting the bellow error.
The data source URL is not accepted by any of the loaded drivers. CLIENT_PLUGIN_AUTH is required
I have placed com.mysql.jdbc.Driver in components/lib folder
what am i missing?
We found an error 'N/A' in column region after enable Geolocation Based Statistics
I have done the steps as follows
Download the geolocation data
Create the database by executing one of the scripts in the Geolocation Data/dbscripts, I use the mysql database
Populate the data to the BLOCKS and LOCATION tables in the database geo_location_data, from the following files Geolocation
Data/data/BLOCKS.csv Geolocation Data/data/LOCATION.csv
Download a JDBC provider for MySQL and Copy the mysql-connector-java.jar to /lib directory
Configure the following in /conf/worker/deployment.yaml file as given below
Configure the following in /wso2/worker/deployment/siddhi-files/IS_ANALYTICS_AUTHENTICATION_COMMON.sidddhi
file as given below
Restart WSO2 IS & WSO2 IS Analytics.
any advice? so that region column can show real location when user access the application
Apart from the above steps, you need to have the proper IPs in order to get it working. It derives the region based on the user IPs. Then you should be able to see the relevant stats as below,
I have a problem when i want to use DirectQuery. I have a DomainController with installed SQL Server. I have installed Data Gateway and must modify the Service Account to Local System to be able to finish setup. i have setup the Data Gateway successfully in Enterprise Mode. In PowerBi.com everything looks fine and can see the Gateway and no errors.
When i now create a new File with a SQL connection and Mode "Import" and publish it to PowerBi.com, then it works fine and when i schedule a refresh, this works fine, too.
But i want to use DirectQuery on a Database table for example. For this scenario i have created a new Power BI File and selected the same database which i already created as DataSet in PowerBI.com under my Gateway. Then i load the data in the file and while trying to load it i am always receiving the following error message:
Create Connections
Alternate credentials for Windows authentication is
not supported in DirectQuery mode. Use your current windows
credentials, supply a database credential or switch to import mode.
In PowerBI.com under Gateways and Data source i have used Windows Authentication and used the Administrator account which has also permission on the Database. I dont know what this message means and i should change. Can someone help me?
it seems that your have a credential problem, I suggest you to go to File->Options and settings->Data source settings, then edit your data source [Edit Permissions...] and specify a valid Windows credential or database credential. After that, click "Refresh" button in the PBIX file.
Hope that helps!
If you cannot open the PBIX file, restart Power BI designer with an empty one and then go to the File, Options as explained above. You will find out that an "alternate" credential has been stored for your data source. Use your current credentials instead. Now, try to open the original PBIX file and it you will see that now Direct Query mode works.