ClickHouse is an open-code columnar DBMS that allows for executing analytical queries in real time based on structured big data.
NOTE. If ClickHouse is set up incorrectly, it may result in data model work restrictions.
To install ClickHouse:
Create the clickhouse-odbc driver manually based on the resources corresponding to the used version of Linux OS and install the driver to a computer with installed BI server.
Install the clickhouse-client driver to a computer with installed BI server.
Grant folder access permissions:
/var/lib/clickhouse/user_files:
sudo chown www-data:www-data /var/lib/clickhouse/user_files
/var/lib/clickhouse:
sudo chmod 755 /var/lib/clickhouse
Restart clickhouse-server:
sudo systemctl restart clickhouse-server
Install the clickhouse-odbc driver to a computer with installed BI server.
Install the clickhouse-client driver to a computer with installed BI server using one of the methods:
In the Docker virtual environment start the clickhouse container:
docker run -d --name clickhouse --volume="<path to folder with temporary files>" --ulimit nofile=262144:262144 clickhouse/clickhouse-server
In the <path to folder with temporary files> specify path to folder with temporary files inside the container. For example: temp:/tmp.
Using the built-in Windows function - Windows Subsystem for Linux (WSL). For details about installing ClickHouse using WSL see the official documentation.
After installing the clickhouse-odbc and clickhouse-client drivers determine the following:
Create the Database object in the repository with connection to the ClickHouse server. A detailed description is given in the Connecting to Relational Databases section.
Create the repository variable EXTRACT_DB. As a value, specify ID of the Database object.
Create a service user in the repository who will have access to required objects (models), set the Login, Login to Object Navigator and Read and Open All Objects privileges.
Start the PP.Util utility under the www-data user in Astra Linux, Ubuntu or the apache user in CentOS, RED OS, Rocky Linux, ALT Linux. Next, save service user credentials. The example of command:
sudo -u www-data PP_NODISPLAY=1 /opt/foresight/fp10.x-biserver/bin/PP.Util /save_creds mb_defenition /DEC login pass
Where:
mb_defenition. Repository identifier.
login. Service user name.
pass. Service user password.
After executing the command service user credentials are saved to the Metabases.xml.
See also: