You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[DH-5733] Support schemas column to add a db connection (#466)
* [DH-5733] Support schemas column to add a db connection
* DBs without schema should store None
* Add ids in sync-schemas endpoint
* Support multi-schemas for refresh endpoint
* Add schema not support error exception
* Add documentation for multi-schemas
* Fix sync schema method
* Sync-schemas endpoint let adding ids from different db connection
* Fix refresh endpoint
* Fix table-description storage
* Fix schema_name filter in table-description repository
* DH-5735/add support for multiple schemas for agents
* DH-5766/adding the validation to raise exception for queries without schema in multiple schema setting
* DH-5765/add support multiple schema for finetuning
---------
Co-authored-by: mohammadrezapourreza <m1378.prz@gmail.com>
##### Connecting to supported Data warehouses and using SSH
182
200
You can find the details on how to connect to the supported data warehouses in the [docs](https://dataherald.readthedocs.io/en/latest/api.create_database_connection.html)
183
201
@@ -194,7 +212,8 @@ While only the Database scan part is required to start generating SQL, adding ve
194
212
#### Scanning the Database
195
213
The database scan is used to gather information about the database including table and column names and identifying low cardinality columns and their values to be stored in the context store and used in the prompts to the LLM.
196
214
In addition, it retrieves logs, which consist of historical queries associated with each database table. These records are then stored within the query_history collection. The historical queries retrieved encompass data from the past three months and are grouped based on query and user.
197
-
db_connection_id is the id of the database connection you want to scan, which is returned when you create a database connection.
215
+
The db_connection_id param is the id of the database connection you want to scan, which is returned when you create a database connection.
216
+
The ids param is the table_description_id that you want to scan.
198
217
You can trigger a scan of a database from the `POST /api/v1/table-descriptions/sync-schemas` endpoint. Example below
Since the endpoint identifies low cardinality columns (and their values) it can take time to complete. Therefore while it is possible to trigger a scan on the entire DB by not specifying the `table_names`, we recommend against it for large databases.
231
+
Since the endpoint identifies low cardinality columns (and their values) it can take time to complete.
213
232
214
233
#### Get logs per db connection
215
234
Once a database was scanned you can use this endpoint to retrieve the tables logs
0 commit comments