Elastic PostgreSQL connector reference
editElastic PostgreSQL connector reference
editThe Elastic PostgreSQL connector is a connector for PostgreSQL.
Availability and prerequisites
editThis connector is available as a native connector in Elastic versions 8.8.0 and later. To use this connector as a native connector, satisfy all native connector requirements.
This connector is available as a connector client from the Python connectors framework. To use this connector, satisfy all connector client requirements.
This connector is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
Usage
editTo use this connector as a native connector, use the Connector workflow. See Native connectors.
To use this connector as a connector client, see Connector clients and frameworks.
Users must set track_commit_timestamp
to on
.
To do this, run ALTER SYSTEM SET track_commit_timestamp = on;
in PostgreSQL server.
For additional operations, see Usage.
For an end-to-end example of the connector client workflow, see PostgreSQL connector client tutorial.
Compatibility
editPostgreSQL versions 11 to 15 are compatible with Elastic connector frameworks.
Configuration
editWhen using the connector client workflow, initially these fields will use the default configuration set in the connector source code.
Note that this data source uses the generic_database.py
connector source code.
Refer to postgresql.py
for additional code, specific to this data source.
These configurable fields will be rendered with their respective labels in the Kibana UI.
Once connected, users will be able to update these values in Kibana.
Set the following configuration fields:
- Host
-
The server host address where the PostgreSQL is hosted. Examples:
-
192.158.1.38
-
demo.instance.demo-region.demo.service.com
-
- Port
-
The port where the PostgreSQL is hosted. Examples:
-
5432
-
9090
-
- Username
- The username of the PostgreSQL account.
- Password
- The password of the PostgreSQL account.
- Database
-
Name of the PostgreSQL database. Examples:
-
employee_database
-
customer_database
-
- Comma-separated List of Tables
-
A list of tables separated by commas. The PostgreSQL connector will fetch data from all tables present in the configured database, if the value is
*
. Default value is*
. Examples:-
table_1, table_2
-
*
-
- Enable SSL
-
Whether SSL verification will be enabled.
Default value is
True
. - SSL Certificate
-
Content of SSL certificate. If SSL is disabled, the
ssl_ca
value will be ignored.Expand to see an example certificate
-----BEGIN CERTIFICATE----- MIID+jCCAuKgAwIBAgIGAJJMzlxLMA0GCSqGSIb3DQEBCwUAMHoxCzAJBgNVBAYT AlVTMQwwCgYDVQQKEwNJQk0xFjAUBgNVBAsTDURlZmF1bHROb2RlMDExFjAUBgNV BAsTDURlZmF1bHRDZWxsMDExGTAXBgNVBAsTEFJvb3QgQ2VydGlmaWNhdGUxEjAQ BgNVBAMTCWxvY2FsaG9zdDAeFw0yMTEyMTQyMjA3MTZaFw0yMjEyMTQyMjA3MTZa MF8xCzAJBgNVBAYTAlVTMQwwCgYDVQQKEwNJQk0xFjAUBgNVBAsTDURlZmF1bHRO b2RlMDExFjAUBgNVBAsTDURlZmF1bHRDZWxsMDExEjAQBgNVBAMTCWxvY2FsaG9z dDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMv5HCsJZIpI5zCy+jXV z6lmzNc9UcVSEEHn86h6zT6pxuY90TYeAhlZ9hZ+SCKn4OQ4GoDRZhLPTkYDt+wW CV3NTIy9uCGUSJ6xjCKoxClJmgSQdg5m4HzwfY4ofoEZ5iZQ0Zmt62jGRWc0zuxj hegnM+eO2reBJYu6Ypa9RPJdYJsmn1RNnC74IDY8Y95qn+WZj//UALCpYfX41hko i7TWD9GKQO8SBmAxhjCDifOxVBokoxYrNdzESl0LXvnzEadeZTd9BfUtTaBHhx6t njqqCPrbTY+3jAbZFd4RiERPnhLVKMytw5ot506BhPrUtpr2lusbN5svNXjuLeea MMUCAwEAAaOBoDCBnTATBgNVHSMEDDAKgAhOatpLwvJFqjAdBgNVHSUEFjAUBggr BgEFBQcDAQYIKwYBBQUHAwIwVAYDVR0RBE0wS4E+UHJvZmlsZVVVSUQ6QXBwU3J2 MDEtQkFTRS05MDkzMzJjMC1iNmFiLTQ2OTMtYWI5NC01Mjc1ZDI1MmFmNDiCCWxv Y2FsaG9zdDARBgNVHQ4ECgQITzqhA5sO8O4wDQYJKoZIhvcNAQELBQADggEBAKR0 gY/BM69S6BDyWp5dxcpmZ9FS783FBbdUXjVtTkQno+oYURDrhCdsfTLYtqUlP4J4 CHoskP+MwJjRIoKhPVQMv14Q4VC2J9coYXnePhFjE+6MaZbTjq9WaekGrpKkMaQA iQt5b67jo7y63CZKIo9yBvs7sxODQzDn3wZwyux2vPegXSaTHR/rop/s/mPk3YTS hQprs/IVtPoWU4/TsDN3gIlrAYGbcs29CAt5q9MfzkMmKsuDkTZD0ry42VjxjAmk xw23l/k8RoD1wRWaDVbgpjwSzt+kl+vJE/ip2w3h69eEZ9wbo6scRO5lCO2JM4Pr 7RhLQyWn2u00L7/9Omw= -----END CERTIFICATE-----
Deployment using Docker
editFollow these instructions to deploy the PostgreSQL connector using Docker.
Step 1: Download sample configuration file
Download the sample configuration file. You can either download it manually or run the following command:
curl https://raw.githubusercontent.com/elastic/connectors-python/main/config.yml --output ~/connectors-python-config/config.yml
Remember to update the --output
argument value if your directory name is different, or you want to use a different config file name.
Step 2: Update the configuration file for your self-managed connector
Update the configuration file with the following settings to match your environment:
-
elasticsearch.host
-
elasticsearch.password
-
connector_id
-
service_type
Use postgresql as the service_type
value.
Don’t forget to uncomment "postgresql" in the sources
section of the yaml
file.
If you’re running the connector service against a Dockerized version of Elasticsearch and Kibana, your config file will look like this:
elasticsearch: host: http://host.docker.internal:9200 username: elastic password: <YOUR_PASSWORD> connector_id: <CONNECTOR_ID_FROM_KIBANA> service_type: postgresql sources: # UNCOMMENT "postgresql" below to enable the PostgreSQL connector #mongodb: connectors.sources.mongo:MongoDataSource #s3: connectors.sources.s3:S3DataSource #dir: connectors.sources.directory:DirectoryDataSource #mysql: connectors.sources.mysql:MySqlDataSource #network_drive: connectors.sources.network_drive:NASDataSource #google_cloud_storage: connectors.sources.google_cloud_storage:GoogleCloudStorageDataSource #azure_blob_storage: connectors.sources.azure_blob_storage:AzureBlobStorageDataSource #postgresql: connectors.sources.postgresql:PostgreSQLDataSource #oracle: connectors.sources.oracle:OracleDataSource #mssql: connectors.sources.mssql:MSSQLDataSource
Note that the config file you downloaded might contain more entries, so you will need to manually copy/change the settings that apply to you.
Normally you’ll only need to update elasticsearch.host
, elasticsearch.password
, connector_id
and service_type
to run the connector service.
Step 3: Run the Docker image
Run the Docker image with the Connector Service using the following command:
docker run \ -v ~/connectors-python-config:/config \ --network "elastic" \ --tty \ --rm \ docker.elastic.co/enterprise-search/elastic-connectors:8.8.2.0-SNAPSHOT \ /app/bin/elastic-ingest \ -c /config/config.yml
Refer to this guide in the Python framework repository for more details.
Documents and syncs
edit- Tables must be owned by a PostgreSQL user.
- Database superuser privileges are required to index all database tables.
- Tables with no primary key defined are skipped.
-
To fetch the last updated time in PostgreSQL,
track_commit_timestamp
must be set toon
. Otherwise, all data will be indexed in every sync.
Sync rules
edit- Permissions are not synced. All documents indexed to an Elastic deployment will be visible to all users with access to that deployment.
- Filtering rules are not available in the present version. Currently filtering is controlled via ingest pipelines.
Content extraction
editSee Content extraction.
Connector client operations
editEnd-to-end testing
editThe connector framework enables operators to run functional tests against a real data source. Refer to Connector testing for more details.
To perform E2E testing for the PostgreSQL connector, run the following command:
$ make ftest NAME=postgresql
For faster tests, add the DATA_SIZE=small
flag:
make ftest NAME=postgresql DATA_SIZE=small
Known issues
editThere are no known issues for this connector. Refer to Known issues for a list of known issues for all connectors.
Troubleshooting
editSee Troubleshooting.
Security
editSee Security.
Framework and source
editThis connector is included in the Python connectors framework.
This connector uses the generic database connector source code (branch 8.8, compatible with Elastic 8.8).
View additional code specific to this data source (branch 8.8, compatible with Elastic 8.8).